Re:Memory Safety in a Modern System Programming Language Pt. 1
by shadowofneptune on Wednesday June 22, 2022 @12:24PM
(#31838099)
What is the quality of support for these rules at the moment in external tools such as linters?
[ Parent
| on HN ]
Re:Memory Safety in a Modern System Programming Language Pt. 1
by dukc on Wednesday June 22, 2022 @02:56PM
(#31840270)
I'm personally kind of anarchic, because I use hardly any tools. Text editor and terminal, that's how I program. The compiler is my linter. So I don't know.
Re:Memory Safety in a Modern System Programming Language Pt. 1
by dukc on Thursday June 23, 2022 @05:28AM
(#31846751)
Used the wrong word. Meant "archaic", not "anarchic".
Side note, D has source code tools, this being probably the most famous one: https://github.com/dlang-community/D-Scanner . It's just that I don't use them myself.
Re:Memory Safety in a Modern System Programming Language Pt. 1
by mhh__ on Wednesday June 22, 2022 @04:32PM
(#31841503)
The rules are enforced by the compiler not a linter.
Linting in a way that requires semantic analysis is not well trodden ground in D tooling.
deadalnix and myself are aiming to rectify this somewhat by ramping up work on sdc, which is basically a D frontend done right.
Re:Memory Safety in a Modern System Programming Language Pt. 1
by WalterBright on Thursday June 23, 2022 @02:05AM
(#31845672)
The idea with D is to not require a linter!