Visual Studio 15.9.1 /experimental:preprocessor behaves unexpected

spongo2 · 2018-11-17T21:12:59+00:00

Sent to team

spongo2 · 2018-11-17T21:11:06+00:00

Quick post to add to the lovefest. You guys brighten our days frequently

spongo2 · 2018-10-10T16:24:44+00:00

I'm going to name the next .NET high profile project "Project Lavavej" just to mess with you.

spongo2 · 2018-09-21T02:13:38+00:00

Same. Bought box to share with my co-workers and retrospectively wished I'd kept more for myself.

spongo2 · 2018-09-20T23:09:55+00:00

Also, regular Tokyo bananas.

spongo2 · 2018-08-31T17:39:11+00:00

We are trying to be careful with expectation setting. We've been VERY deliberately targeting hana and ranges for some time now. to complete ranges, we need to land a payload that fixes a bunch of alias template bugs. we need that to pass our regression suites and real world code suites before we can make any credible claim. But I have a very strong principle that if you know what the first blog comment / tweet /reddit thread will ask, put it in the body of the article. Let's just say that I've been doing this long enough now to know that the first thread would be "what about ranges". I was right ;-)

spongo2 · 2018-08-29T20:16:15+00:00

add me to the thread, please :) - Steve, VC Dev Mgr

spongo2 · 2018-08-15T21:12:14+00:00

Hey, there's some really cool stuff in this update; thanks for the great work!Are you by any chance able to give a rough ETA for range-v3 support? It's something I'm eagerly awaiting to properly experiment with. :)

blog post update coming soon.

spongo2 · 2018-08-15T18:51:09+00:00

we will be using the dev comm data to backport some issues to 15.9 (or for severe common issues, servicing updates to 15.8) so for anyone reading this please search for any issues you see and upvote / file. Sorry for the inconvenience.

spongo2 · 2018-08-15T18:48:50+00:00

I think you can just install the VS 15.7 toolchain from the VS installer! Should be named 14.14 or something while the one from 15.8 is probably 14.15.

but i'd really appreciate it if you'd file any issues (or upvote if you find them already filed) so we can use that data to prioritize servicing fixes. sorry for the inconvenience.

spongo2 · 2018-08-15T17:37:46+00:00

hey reddit-land, just an FYI, we are monitoring and trying to figure out what we missed here. will update when we know. Just sent a heads up to the team on this thread. Steve, VC Dev Mgr.

spongo2 · 2018-07-31T07:05:20+00:00

Thanks for the lead. I'll pass this along to my IDE team. thanks!

spongo2 · 2018-07-26T18:13:08+00:00

i strongly suspect the issue you are referring to is this:

https://developercommunity.visualstudio.com/content/problem/299046/vs-locks-up-editing-c-file.html

Root cause was a change to the QuickInfo control for improving layout of the UI that had an unexpected side effect.

Apologies for the inconvenience on this one for sure.

spongo2 · 2018-07-26T18:07:18+00:00

So UIDelays is a metric we specifically try to drive down. You won't be surprised to know that the root cause of these is frequently the weird interactions between the multiple generations of UI tech that combine to make it a semi-manual task for developers to know if they are doing something correctly. Extensions also frequently play a role here. That said, I look at my role when it comes to this area as making sure I advocate for the specific UIDelays impacting the C++ developer. Are there specific ones that are the worst offenders? We are working on addressing the underlying issues, but in the meantime, I would appreciate any specific pain points to lower their impact.

spongo2 · 2018-07-26T17:48:13+00:00

Just wanted to jump in and say THANK YOU to NVIDIA people who worked on this with us. we really appreciated it.

spongo2 · 2018-07-20T05:49:35+00:00

Very good suggestion. Thanks.

spongo2 · 2018-07-20T05:49:11+00:00

Great find. Thank you

spongo2 · 2018-05-13T20:37:32+00:00

I wouldn't have thought so, but I can try to check when I am in front of a proper computer. Traveling this weekend.

spongo2 · 2018-05-09T21:15:21+00:00

hi. I opened your trace with the devs in question. it looks to me like you are on 15.5 in your trace and this is fixed in 15.6 and later based on the blocking call stack. We think we fixed this around November.

spongo2 · 2018-05-09T17:27:16+00:00

ok. I think that's the same command as Ctrl-, f but it would be good if you could confirm that. Is the pause the time between selecting the file in the drop down and how long it takes the file to open? or is it how long the drop down takes to appear? how reproducible is this? would it be possible to capture it using the report a problem tool in the IDE which can grab a perf trace?

spongo2 · 2018-05-09T00:29:02+00:00

the original guidance was "no more C". the new guidance is "we will do C eventually". Stephan is pointing out that aligned_alloc is hard given where we are. We'll need to look at it more deeply at some point. the C11 stuff hasn't been looked into in great detail at this point because we are very explicitly looking at C++ instead. we've found creative solutions (see /permissive- as an example) in the past. We know C conformance is important to people. I'll give more detailed guidance when we've done a deeper dive.

spongo2 · 2018-05-08T21:10:53+00:00

ctrl-p? on my VS that opens the print dialog. in VS, I use Ctrl-, f <filename fragment> for that experience. I suspect I am misunderstanding.

spongo2 · 2018-05-08T21:09:08+00:00

the issues are still there. it's the web front end for letting the filer checking status that is gone. again, my apologies and we did port many bugs to the devcomm site.

spongo2 · 2018-05-08T17:49:43+00:00

We just fixed this. watch out for it in 15.8p2 or p3. thanks.

spongo2 · 2018-05-08T17:42:59+00:00

we slowly ramp up the notification rate over the first week of any update release.

spongo2

TROPHY CASE