-
-
Notifications
You must be signed in to change notification settings - Fork 206
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
feat: add cpp dictionary files #1101
Conversation
Great, I'll pull these in. Please note, it is not necessary to comment out short words like
I think it is better to leave them in. It will not hurt performance. |
I'll combine these into a new dictionary. Any suggestions on a name? Note: Some people have the minimum word length set to 2, which is why it is useful to have the short words in the dictionary. |
@david-fong, |
cpp-refined sounds good to me. cpp-dict-v2 could be another option. up to you. my pleasure! I'm working on a c++ project so I'm benefitting from it too :) thanks for being so responsive and for maintaining this project! I'll probably want to make some more future additions. Ex. some boost library words, or words for more compiler builtins, or very-popular libraries. Let me know if there's a procedure / format for how best to do that. |
I have wired everything up in #1102. |
wonderful! looking forward to the next release :) |
not sure where to say this. I just found out cppreference has a "symbol index" page that looks like it could be useful as an information source for some kind of automation (as opposed to how I did things manually). |
That looks like a good resource. It might be possible with a This is their API: https://en.cppreference.com/mwiki/api.php Since they are using the Creative Commons License, it is possible to use it. |
Just open a new issue to track using cppreference as a source. |
for #54
I've left out my boost-library file for now since it's not finished yet.
Should I make any changes to the json files in this PR? Or can I leave that to you?