libbooze

> As the proposal discusses, it isn't clear there _is_ a sensible default in many cases. We have a specific concern with initializing variables to non-sensible "default" values and being...

> I think the primary reason is we can’t build numpy in debug mode(with the debug version msvcrt). ONNX and ONNX Runtime follow the same pattern. Either they all define...

> 1. The example presented in the paper isn't specifically (IIUC) asserting that such a change would be a performance win for the member functions of string_view. (Or at least,...

> Our _interoperability_ and _migration_ goals are completely separate from what version we use when building the Carbon Explorer itself, or to write the toolchain. Those will obviously have to...

> FWIW, #2365 aims to remove the confusion here somewhat. For me this closes the issue, would be nice if we would have more details, e.g. what about modules or...

> I find that treating an omitted initializer as meaning "pick a specific default value" is error-prone and optimizes for the writer at the expense of the reader and potentially...

@pdimov brainbending, but amazing... I could not understand how you can use E(value, not type) as template parameter, but it is of integral_constant kind of thing so that is why...

@pdimov I was assuming mp_enum could "remember" the enum class it "came from"(using enum_type = ....) while behaving mostly like integral_constant, but then when "assignments" happen from another mp_enum you...

> Thanks for reporting, I'll update that example in the next release. Thank you. Maybe also mention that `co_yield` return value is how `x` gets updated in the example. I...

Awesome, thank you for the reply. I would move that to readme to make it more obvious, but beside that I think this issue can be closed.