On 1/8/16, 12:11 PM, "Josh Tynjala" <joshtynj...@gmail.com> wrote:
>I should add that I strongly agree with Andy that we shouldn't change the >default behavior of the existing forms of casting. That's why I made the >above proposal for a special function that the emitter would know to strip >away. It would allow us preserve the existing casting behavior, while >providing a separate option that simply makes the compiler and IDEs happy. >It's something additional to learn instead of discovering that what you >already learned is now completely wrong. I think that's safer and less >likely to make people angry and frustrated. I don't feel like I'm changing behavior. I think I'm trying to implement some compiler optimizations via hinting. For sure I will make sure there are enough knobs so the compiler doesn't try to optimize at all. And when you set the flag to not remove circular requires, then we'll see how folks feel about re-writing their code to deal with it. I think the feedback we've received so far is that we need to do some of this stuff because some folks don't want to massage their code that much. The more they have to massage, the more likely they are to just port to some other framework/language. -Alex
