Skip to content
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

[BUG] C++ standard not captured #15

Open
drok opened this issue Apr 1, 2024 · 0 comments
Open

[BUG] C++ standard not captured #15

drok opened this issue Apr 1, 2024 · 0 comments

Comments

@drok
Copy link
Contributor

drok commented Apr 1, 2024

Describe the bug

When changing the language version of a C++ project, IntelliSense is not configured with the new standard.
This causes IntelliSense to mark as errors language features which are in fact supported (eg, std::string_view is supported in C++ 17 and later)

Steps to reproduce the behavior:

Expected behavior

IntelliSense C++ language standard configuration should be updated immediately when changed in the project

Where does the extension run?

  • OS where VSCode runs: Windows 10
  • OS where the autotools extension runs: Ubuntu 16
  • Extension Version: 0.2.0

What project are you editing?

  • Repo: [private]
  • Autoconf version (autoconf --version): 2.69
  • Automake version (automake --version): 1.15
  • Make version (make --version): 4.1
  • Using libtool? : no

Additional context

Add any other context about the problem here.

What does the extension log? (OUTPUT pane / "Autotools" channel)

2024-04-01T14:45:03.384Z: starting mergesium.autotools 0.2.0/linux-x64 - pre-release expires 2024-04-15
Package "ad7proxy" version 1.0.0 - bug reports: unknown, url: unknown
Knowledge Base: https://autotools.mergesium.com/kb/ad7proxy?v=1.0.0
Writing the dry-run output: /home/radu/my-proj/build/Debug/.vscode/all.dryrun.log
Exported to Intellisense: build configuration for 2 source files like ad7proxy.cpp, ad7proxy-test.cpp, ...
Generated tasks: 2 build tasks and 1 test tasks in 1 check suites (see Run Task... command)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant