deno_lint
llvm-project
Our great sponsors
deno_lint | llvm-project | |
---|---|---|
11 | 348 | |
1,499 | 25,451 | |
0.3% | 3.6% | |
8.6 | 10.0 | |
8 days ago | about 23 hours ago | |
Rust | C++ | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
deno_lint
- Configuring ESLint, Prettier, and TypeScript Together | Josh Goldberg
-
Porting 58000 lines of D and C++ to jai, Part 0: Why and How
Fast compilation seems very appealing. It is one of the main reason why I am interested into Go and Zig.
I recently started working with Rust for contributing to projects like Rome/tools [1] and deno_lint [2]. The compilation and IDE experience is frustrating. Compilation is slow. I am afraid that this is rooted to the inherent complexity of Rust.
-
Deno 1.28: Featuring 1.3M New Modules
Though, for large scale projects, I’d wait until https://github.com/denoland/deno_lint/issues/303 is done; if they tackle that, they tackled types, and that’s the single big thing yet to tackle.
-
Everytime I use Deno.js it is harder to go back to Node.
There isn't any uniformity that could be reasonably achieved once plugins are added to a linter. Someone will always want an edge case for their project covered even if it's not in the uniform configuration; most large projects either use plugins or custom rules outside of what ESLint provides. Deno understands this too given that plugin support is being considered.
-
Fresh framework IDE & Lint Config?
Deno's lint config is under deno.json or deno.jsonc and is limited to the following rules: https://lint.deno.land/
-
Learning TypeScript? try Deno
$ deno lint (prefer-const) `order` is never reassigned let order = new Order() ^^^^^ at /Users/dina/try-deno/design-patterns/state.ts:106:4 hint: Use `const` instead help: for further information visit https://lint.deno.land/#prefer-const Found 24 problems Checked 25 files
-
deno_lint VS ESLint - a user suggested alternative
2 projects | 24 Dec 2021
-
deno_lint VS quick-lint-js - a user suggested alternative
2 projects | 24 Dec 2021
-
Rust Is The Future of JavaScript Infrastructure
I built one of the tools mentioned in the article, Deno's linter. Its binary is over 30 MiB:
-
OSS Contributions: 16th-23rd August 2021
After a long time, I started contributing to open-source software. For a long time, I had my eye on Deno. This week, I merged my first PR in Deno Lint. Following is the detailed post about the issue.
llvm-project
- Flang-new: How to force arrays to be allocated on the heap?
- The LLVM Compiler Infrastructure
-
Programming from Top to Bottom - Parsing
You can never mistake type_declaration with an identifier, otherwise the program will not work. Aside from that constraint, you are free to name them whatever you like, there is no one standard, and each parser has it own naming conventions, unless you are planning to use something like LLVM. If you are interested, you can see examples of naming in different language parsers in the AST Explorer.
-
Look ma, I wrote a new JIT compiler for PostgreSQL
> There is one way to make the LLVM JIT compiler more usable, but I fear it’s going to take years to be implemented: being able to cache and reuse compiled queries.
Actually, it's implemented in LLVM for years :) https://github.com/llvm/llvm-project/commit/a98546ebcd2a692e...
-
C++ Safety, in Context
> It's true, this was a CVE in Rust and not a CVE in C++, but only because C++ doesn't regard the issue as a problem at all. The problem definitely exists in C++, but it's not acknowledged as a problem, let alone fixed.
Can you find a link that substantiates your claim? You're throwing out some heavy accusations here that don't seem to match reality at all.
Case in point, this was fixed in both major C++ libraries:
https://github.com/gcc-mirror/gcc/commit/ebf6175464768983a2d...
https://github.com/llvm/llvm-project/commit/4f67a909902d8ab9...
So what C++ community refused to regard this as an issue and refused to fix it? Where is your supporting evidence for your claims?
-
Clang accepts MSVC arguments and targets Windows if its binary is named clang-cl
For everyone else looking for the magic in this almost 7k lines monster, look at line 6610 [1].
[1] https://github.com/llvm/llvm-project/blob/8ec28af8eaff5acd0d...
-
Rewrite the VP9 codec library in Rust
Through value tracking. It's actually LLVM that does this, GCC probably does it as well, so in theory explicit bounds checks in regular C code would also be removed by the compiler.
How it works exactly I don't know, and apparently it's so complex that it requires over 9000 lines of C++ to express:
https://github.com/llvm/llvm-project/blob/main/llvm/lib/Anal...
- Fortran 2023
-
MiniScript Ports
• Go • Rust • Lua • pure C (sans C++) • 6502 assembly • WebAssembly • compiler backends, like LLVM or Cranelift
-
On Avoiding Register Spills in Vectorized Code with Many Constants
Compilers also may even spill data to stack from memory, even when the original location is still available, as can be seen in this issue: https://github.com/llvm/llvm-project/issues/53348
I vaguely remember that spilling like this could allow high-end CPUs to use something similar to register renaming, i.e. stack locations like [rsp + 96] could be stay in a physical registers during function execution (high-end CPUs often have more physical registers, than logical ones), but could find good references whether such optimization exists in practice or not.
Unfortunately, I think more often than note it causes performance regressions and in some cases it may even cause unnecessary stack spilling of sensitive data: https://github.com/rust-lang/rust/issues/88930#issuecomment-...
What are some alternatives?
rslint - A (WIP) Extremely fast JavaScript and TypeScript linter and Rust crate
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
dprint - Pluggable and configurable code formatting platform written in Rust.
Lark - Lark is a parsing toolkit for Python, built with a focus on ergonomics, performance and modularity.
deno_sdl2 - SDL2 module for Deno
gcc
RSLint - A (WIP) Extremely fast JavaScript and TypeScript linter and Rust crate [Moved to: https://github.com/rslint/rslint]
SDL - Simple Directmedia Layer
dvm - 🦕 Deno Version Manager - Easy way to manage multiple active deno versions.
cosmopolitan - build-once run-anywhere c library
quick-lint-js - quick-lint-js finds bugs in JavaScript programs
windmill - Open-source developer platform to turn scripts into workflows and UIs. Fastest workflow engine (5x vs Airflow). Open-source alternative to Airplane and Retool.