Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing Semgrep and r2c

r2c.dev

Post reply on HN
Print view View original

21–23 of 23 posts

Re: Introducing Semgrep and r2c

#21

Post by philsnow »

inetknght wrote: post #20
carlmr wrote: post #15

Earlier quoted context omitted.

The preprocessed output of GCC and Clang usually contains the file names.

Better than that, compilers can be told to include line numbers too. This thread would love to learn about Compiler Explorer https://gcc.godbolt.org/ which works for C++ and many other languages.

Line numbers are a good start, but JS source maps go from output source byte ranges to input source byte ranges.

I don't write or even read a lot of C++ these days but I recall from when I did that a major pain point was deciphering compiler warnings/errors when there are a lot of templates, macros, or both. Seems like the problem has been around forever.

Re: Introducing Semgrep and r2c

#22

Post by rtsao »

It's great to see more tools adopting tree-sitter [1].

Having a (fast) single tool that can accurately parse most commonly used programming languages is incredibly useful, but it requires the maintenance of dozens of grammars, which is difficult without a large community effort. Hopefully increased adoption means more accurate parsers and support for even more languages.

Tree-sitter powers syntax highlighting on GitHub.com and (soon) neovim and OniVim 2. Hopefully regex-based syntax highlighting is a thing of the past soon. If you haven't seen the Strange Loop conference talk on tree-sitter [2] yet, it's worth a watch.

I think a Prettier-like code formatter using tree-sitter would be cool, both in terms of potentially broader language support and native performance.

[1]: https://tree-sitter.github.io/tree-sitter/

[2]: https://www.youtube.com/watch?v=Jes3bD6P0To

Post reply on HN