-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use c++17 for non-c files #64
Conversation
Blocking this on tree-sitter/tree-sitter-haskell#38 for Windows support in CI |
Don't C++17 features mean commands like |
Probably. I think I mentioned in the Haskell thread, tree sitter probably needs a better standardized approach to building C++ parsers. |
This is no longer needed for tree-sitter-haskell, as that external scanner has been rewritten in plain C. |
ah perfect. let me get the test-haskell branch up to date with that then close this PR, this issue is where I got stuck previously |
Haskell looks to be failing on Windows Python 3.5 runner even with the new C parser: https://github.com/tree-sitter/py-tree-sitter/runs/5104795690?check_suite_focus=true |
The Haskell scanner uses |
I would like to see this change land. On macOS, when trying to compile 'scanner.cc', the /usr/bin/cc compiler is invoked. $ cc --version And this compiler defaults to not supporting C++ at all. My particular example scanner.cc uses C++17 features, so this patch would be ideal. |
Alternately, it would be sufficient to be able to pass compiler flags down through the interface. |
Haskell's scanner is now back in C, and no we do not want to encourage using modern standards/features in a scanner, it is just not needed. |
https://github.com/tree-sitter/tree-sitter-haskell uses
c++17
language features, so needs to be built with that flag.Test output: