C2SP
Transparency of the project
Could we please have more transparency what is happening with this project to avoid unnecessary and parallel work.
At this point I have rewritten a significant part of the test vector generation for Wycheproof, just so that I can continue with the project. Without some coordination even more time might be wasted, which could be used for solving new issues instead. At this point I don't know who is interested in the project and what potentially outstanding issues are.
For example it would be helpful to have just a list of cryptographic primitives and their status (i.e. whether they are supported, whether test vectors have been tested or which party might be interested to use them)
@ibobak does this issue reproduce when you disable the Pylance extension?
I disabled pylance, restarted vs code, and how I have this problem:
How can it be? Why can't I rename the variable as it was done before?
I re-enabled Pylance, restarted the language server, and now it works as it was before:
To be honest, I don't know the reason why renaming was not working at all while pylance was not loaded. But I actually googled the solution "renaming symbol is not working in VS code", and the answer was "enable pylance and restart language server" :)
So, is there some way to make it NOT renaming the symbol everywhere, but to do this just inside the function?
The issue is now with the "info needed" label. Do you need some other info from me? If yes, feel free to ask.
