-
This is a feature request to add support for JSDoc to more rules. When linting javascript files using `typescript-eslint`, some rules work like `no-floating-promise` because its a rule that works in J…
-
Use the `pratt` parser crate.
We probably need to drop support for spaces in identifiers for this though.
-
https://github.com/rdaum/moor/blob/f0ad4fddb4685fd980edace998a91b5f30d99317/crates/compiler/src/unparse.rs#L38
```rust
// directly on http://en.cppreference.com/w/cpp/language/operator_prece…
-
https://github.com/rdaum/moor/blob/a951a75fbd22306ec6e29d403eb9d7cd7d88b405/crates/compiler/src/unparse.rs#L38
```rust
// directly on http://en.cppreference.com/w/cpp/language/operator_prece…
-
## Motivation
Maybe related to https://github.com/gajus/eslint-plugin-jsdoc/issues/145
I'm using JavaScript (not TypeScript), but I still want to import TypeScript type in inline fashion.
…
yvele updated
8 months ago
-
## Expected behavior
With the following snippet the TypeScript language service correctly displays the JSDoc when inspecting the function, and I expect `jsdoc/require-jsdoc` to know the f…
-
I get a stack overflow when running any of the tests for this library. I tried to look over similar issues to figure out what I'm doing wrong but I've had no luck. I'm using verion 1.0.0-alpha.6.
E…
-
-
-
The current expression parsing code is a bit long (using recursive descent for resolving the operators' precedence) and is taking many function calls to parse a single integer literal:
```
parseExpr…