David Else

@diannasoreil I am using Neovim, there is no instructions at https://github.com/rust-lang/rustlings#enabling-rust-analyzer how to make rust-analyzer work other than with vs-code and IntelliJ-based editors. The README says to `curl -L https://raw.githubusercontent.com/rust-lang/rustlings/main/install.sh...

@diannasoreil Thanks for the info, it was very helpful! If you did include the exercises/ subfolder in the project so `rust-analyzer` worked, would that negatively affect any users? If not,...

@jackos @diannasoreil Thanks! This is great news :)

I am using the LSP/linter for browser code, and adding `/// ` at the top of modules that require it. I can use the `.ts` extension for local imports and...

@bartlomieju Can I turn off `no-undef` per module like eslint's `/* eslint-disable */`?

@bartlomieju Would be great to get that added to the docs. I did search for the information before but found nothing.

Great news it is easy to do! I think `deno lint` itself is ready, but if you think the extension implementation needs more work, I really look forward to it...

I have not looked into if this is being done already by deno_lint, but when TypeScript is being used then the `"plugin:@typescript-eslint/eslint-recommended"` rules should override the `eslint-recommended` rules. This is...

I think the original ESLint rule `prefer-arrow-callback` does what you want with no extra strict settings: https://eslint.org/demo#eyJ0ZXh0IjoiY29uc3QgRGVubyA9IHt9O1xuXG5mdW5jdGlvbiBiYXIoKXt9XG5iYXIoKVxuXG5EZW5vLnRlc3QoXCJmb29cIiwgZnVuY3Rpb24gKCkgeyAvKiAuLi4gKi8gfSk7Iiwib3B0aW9ucyI6eyJwYXJzZXJPcHRpb25zIjp7ImVjbWFWZXJzaW9uIjoxMSwic291cmNlVHlwZSI6InNjcmlwdCIsImVjbWFGZWF0dXJlcyI6e319LCJydWxlcyI6eyJjb25zdHJ1Y3Rvci1zdXBlciI6MiwiZm9yLWRpcmVjdGlvbiI6MiwiZ2V0dGVyLXJldHVybiI6Miwibm8tYXN5bmMtcHJvbWlzZS1leGVjdXRvciI6Miwibm8tY2FzZS1kZWNsYXJhdGlvbnMiOjIsIm5vLWNsYXNzLWFzc2lnbiI6Miwibm8tY29tcGFyZS1uZWctemVybyI6Miwibm8tY29uZC1hc3NpZ24iOjIsIm5vLWNvbnN0LWFzc2lnbiI6Miwibm8tY29uc3RhbnQtY29uZGl0aW9uIjoyLCJuby1jb250cm9sLXJlZ2V4IjoyLCJuby1kZWJ1Z2dlciI6Miwibm8tZGVsZXRlLXZhciI6Miwibm8tZHVwZS1hcmdzIjoyLCJuby1kdXBlLWNsYXNzLW1lbWJlcnMiOjIsIm5vLWR1cGUtZWxzZS1pZiI6Miwibm8tZHVwZS1rZXlzIjoyLCJuby1kdXBsaWNhdGUtY2FzZSI6Miwibm8tZW1wdHkiOjIsIm5vLWVtcHR5LWNoYXJhY3Rlci1jbGFzcyI6Miwibm8tZW1wdHktcGF0dGVybiI6Miwibm8tZXgtYXNzaWduIjoyLCJuby1leHRyYS1ib29sZWFuLWNhc3QiOjIsIm5vLWV4dHJhLXNlbWkiOjIsIm5vLWZhbGx0aHJvdWdoIjoyLCJuby1mdW5jLWFzc2lnbiI6Miwibm8tZ2xvYmFsLWFzc2lnbiI6Miwibm8taW1wb3J0LWFzc2lnbiI6Miwibm8taW5uZXItZGVjbGFyYXRpb25zIjoyLCJuby1pbnZhbGlkLXJlZ2V4cCI6Miwibm8taXJyZWd1bGFyLXdoaXRlc3BhY2UiOjIsIm5vLW1pc2xlYWRpbmctY2hhcmFjdGVyLWNsYXNzIjoyLCJuby1taXhlZC1zcGFjZXMtYW5kLXRhYnMiOjIsIm5vLW5ldy1zeW1ib2wiOjIsIm5vLW9iai1jYWxscyI6Miwibm8tb2N0YWwiOjIsIm5vLXByb3RvdHlwZS1idWlsdGlucyI6Miwibm8tcmVkZWNsYXJlIjoyLCJuby1yZWdleC1zcGFjZXMiOjIsIm5vLXNlbGYtYXNzaWduIjoyLCJuby1zZXR0ZXItcmV0dXJuIjoyLCJuby1zaGFkb3ctcmVzdHJpY3RlZC1uYW1lcyI6Miwibm8tc3BhcnNlLWFycmF5cyI6Miwibm8tdGhpcy1iZWZvcmUtc3VwZXIiOjIsIm5vLXVuZGVmIjoyLCJuby11bmV4cGVjdGVkLW11bHRpbGluZSI6Miwibm8tdW5yZWFjaGFibGUiOjIsIm5vLXVuc2FmZS1maW5hbGx5IjoyLCJuby11bnNhZmUtbmVnYXRpb24iOjIsIm5vLXVudXNlZC1sYWJlbHMiOjIsIm5vLXVudXNlZC12YXJzIjoyLCJuby11c2VsZXNzLWNhdGNoIjoyLCJuby11c2VsZXNzLWVzY2FwZSI6Miwibm8td2l0aCI6MiwicmVxdWlyZS15aWVsZCI6MiwidXNlLWlzbmFuIjoyLCJ2YWxpZC10eXBlb2YiOjIsInByZWZlci1hcnJvdy1jYWxsYmFjayI6Mn0sImVudiI6e319fQ==

Looking at it again, you are right, it is not _enforcing_ the use of top-level function syntax, just allowing it.