Phillip Carter
Phillip Carter
Yep, contributions welcome for this. I'd say that a new doc called "Performance" under the "Automatic" folder would work.
Labeling, though given that this is explicitly marked as "fast path" and the C# behavior, this may be by design.
I'm perfectly in favor of this getting adjusted, I'm just a bit hesitant to advocate for that given the space. Lack of tests for that behavior is promising w.r.t making...
FWIW I would be in favor of: * Enable a bunch of these fixes by default for everyone * Have a straightforward setting in project files to go back to...
@matthewcrews since @dsyme created the issue I believe he intends on implementing the functions, but I think it would be illustrative to give some examples of how you'd use these...
I can't speak towards this issue since it may be related to the initial design of the compiler, but there are all sorts of little weird things that can happen...
Another thing to keep in mind here is that this can basically bring any editor to a crawl. Here's VS on my laptop (granted, via Parallels) This is just from...
IMO that message constitutes a bug, we should never emit that as a real message.
@bootswithdefer could you sign the CLA? Thanks!
closing old PR