Brad Chamberlain

OK, thanks for clarifying and updating. That sounds consistent with the incorrect behavior I was seeing. I.e., if the compiler is trying to bind the last argument to `repeat` rather...

Whew! I thought you were describing the dyno resolver in your first paragraph. I completely agree that fixing issues in the production resolver that aren't very simple doesn't make sense...

> This need not happen on release day, in fact there might be some benefit in performing this update after code freeze but before the release is officially announced. Dan,...

I think I'm missing something: While I understand the goals of "assume all my values are within range to avoid execution-time overhead that I don't think will be necessary in...

Do GPUs provide hooks like this that would permit such exceptional conditions to be caught without overhead? (my guess would be that at least some don't?).

These recent comments make me wonder whether floating point modes and changes to them (if any) should perhaps be done via methods on locale types (rather than global flags or...

> Separately, it occurs to me that this issue is really proposing two things: > 1. A compilation mode where the compiler can assume it does not need to propagate...

I've added a "user issue" label to this given @redhatturtle's comment above. It's been years since I've looked at or thought about this issue, but reviewing Michael's [C / gcc...

> Not sure exactly what approach we need, but if I were to work on it, the first place I would look is how clang handles it (or if it...

@redhatturtle: I had hoped to find time to prototype this this week, but failed to do so (even though it seemed more fun than everything else I had to do...