Patrick Meinecke

Definitely a bug. Here's a [gist with the disassembly](https://gist.github.com/SeeminglyScience/886087f84ee7462893a2bb77f6b66002). When an assignment like this happens, the output pipe is temporarily changed to a new one that just writes to a...

Tbh I'm not 100% sure why it flushes there at all, it seems like a logic flaw. I can't quickly think of a case where we make a temporary output...

> I think the original title of this issue was a bad choice because it emphasised the failure to parse rather than the difference between versions. ~~The encoding difference is...

> I disagree. Correct me if I'm wrong but `$OutputEncoding` is a setting that controls how the output of cmdlets will be encoded. Oops you're right it doesn't apply here....

#10824 might be related

Believe it or not, there's no actual type accelerator associated. I would have thought that the compiler would skip type resolution for it though, since it doesn't actually use the...

> I think there are 2 problems worth discussing here: > > 1. `[ordered]` is treated as a special attribute solely for the syntax `[ordered] + `. Is that something...

> Would a type accelerator be able to initialize the OrderedDictionary, then add the items of the hashtable? It wouldn't change runtime behavior of anything that currently works. It just...

Yeah there's no scenario that duplicate using namespace declarations would *enable* something. The break scenario is that there might be some script with duplicates that didn't end up using any...

> i'm seeing a strange behavior between scripted and interactive use: here's a transcript: FWIW that's the same behavior that it currently has. It remembers the last set of `using...