Whenever I see people talk about the portability or compatibility advantages of C, I'm reminded of how "even C isn't compatible with C", because you typically aren't talking about up-to-date GCC or LLVM on these niche platforms... you're talking about some weird or archaic vendor-provided compiler... Possibly with syntax extensions that static analyzers like splint will choke on. (Splint can't even understand near... Source: over 1 year ago

Huh. I think I actually needed to use the equivalent position for certain splint annotations in my C retro-hobby project. Source: over 1 year ago

I often like to say that Rust's bindings are a way to trick people into writing the compile-time safety annotations that they didn't want to write for things like splint. (Seriously. Look into how much splint is capable of checking with the correct annotations.). Source: over 1 year ago

Linters like Splint [0] can do that for C. I’m not saying that Rust’s built-in approach isn’t better, but please be careful about what exactly you claim. [0] http://splint.org/. - Source: Hacker News / over 1 year ago

(Sort of like how, for my DOS hobby project, I use splint to require explicit casts between typedefs so I can use the newtype pattern without having to manually reach into wrapper struct fields in places that don't do conversions.). Source: almost 2 years ago

A big part of my work revolves around JavaScript tooling, and as such it's important to keep an eye on the ecosystem and see where things are going. It's no secret that recently lots of projects are native-ying (??) parts of their codebase, or even rewriting them to native languages altogether. Esbuild is one of the first popular and successful examples of this, which was written in Go. Other examples are Rspack... - Source: dev.to / 2 days ago

ESLint: A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. - Source: dev.to / 28 days ago

Automating code checks with static code analysis allows us to enforce code styling effectively. By integrating tools into our workflow, we can identify errors at an early stage, while coding instead of blocking us at the end. For instance, flake8 checks Python code for style and errors, eslint performs similar checks for JavaScript, and prettier automatically formats code to maintain consistency. - Source: dev.to / about 1 month ago

If you're a developer, you're surely familiar with Prettier and ESLint. With over 8 years of existence, they have established themselves as references in the JavaScript ecosystem. - Source: dev.to / about 1 month ago

No lint errors: The committed code does not contain any lint errors (eslint). - Source: dev.to / about 1 month ago