The sgconfig.yml handles platform-specific parsers straightforwardly:
customLanguages:
rescript:
libraryPath: # paths to dynamic library
aarch64-apple-darwin: ./parsers/mac.so
x86_64-unknown-linux-gnu: ./parsers/linux.so
I have working Linux and Mac parser files locally, so I think we now have everything we need. It would now be a question of designing the DX/UX of the linter. How should it fit into the development workflow, and most importantly, how should rules work? Getting into some highly complex extensibility territory like eslint seems unattractive…
@zth do you have thoughts on any of this?