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

[C++] using a operator() of a templated class leads to wrong syntax highlighting results #3315

Closed
gnaggnoyil opened this issue Feb 23, 2016 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Milestone

Comments

@gnaggnoyil
Copy link

This piece of code:

template <typename T>
struct bar{
    int operator()(char x){
        return 0;
    }
};

struct foo:public bar<int>{
    using bar<int>::operator();
};

seems to produce wrong syntax highlighting results for ollowing class/struct declarations/definations and endif macros. On my workspace(VSCode 0.10.8 with Dark+ (default dark) color scheme) it behaves like this:

wrong syntax highlighting

Other macros including define, include, if and ifdef are not affected though.

@aeschli aeschli changed the title C++: using a operator() of a templated class leads to wrong syntax highlighting results [C++] using a operator() of a templated class leads to wrong syntax highlighting results Mar 7, 2016
@aeschli
Copy link
Contributor

aeschli commented Mar 7, 2016

This issue was moved to textmate/c.tmbundle#36

@aeschli aeschli closed this as completed Mar 7, 2016
@aeschli aeschli reopened this Mar 7, 2016
@aeschli aeschli added languages-basic Basic language support issues feature-request Request for new features or functionality bug Issue identified by VS Code Team member as probable bug upstream Issue identified as 'upstream' component related (exists outside of VS Code) and removed languages-basic Basic language support issues labels Mar 7, 2016
@aeschli aeschli added this to the Backlog milestone Mar 7, 2016
@aeschli aeschli removed the feature-request Request for new features or functionality label Mar 17, 2016
@aeschli
Copy link
Contributor

aeschli commented Feb 21, 2017

Closing as the issue is upstream.

@aeschli aeschli closed this as completed Feb 21, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

2 participants