shimaowo

Just seconding the view that the interface inconsistency is actually broken. Anything that can be serialized should successfully deserialize, and vice-versa. I'm all for stripping names unless opted-in, but that...

This wasn't really intended to be a philosophical discussion of whether bf16 is appropriate, but more like "hey, a PR was made and merged here that added support for a...

I confirmed this as well with a simple hello world program using iostream, where 1.19.9 works and 1.20.5 fails. I tried manually forcing the compiler path (typically not required with...

So in the simple cmake hello world project that has the same issue, the c/c++ Log diagnostics is present. I'm not sure why it isn't in the larger project, but...

Here's the debug output - lot of messages about failing to configure the compiler, despite it finding the correct path. ``` loggingLevel: Debug LSP: (received) cpptools/initialize (id: 1) LSP: (invoked)...

Yes, that is the correct path for my current compiler. My VS tools are up to date, but I don't remember when I last upgraded them - not within the...

Debug output: (still some failures, but it eventually finds it. Main difference is this version properly indexes the installed windows kit, whereas 20.5 seems not to find it.) Note that...

No new info in it, but I put the simple test project [here](https://github.com/shimaowo/broken_cpp_vsix), along with the related logs. (They are the same as here, it's just easier for me to...

@sean-mcmanus Confirming this appears fixed in 1.21.0 with quick testing of a few projects that were affected. Thanks!

An update to this, for anyone else looking, since the dev is active elsewhere but seems to have abandoned this project: There is (~1yr old) documentation available [here](https://suvam0451.github.io/docs/sleeping-forest/getting-started/), at least...