I don't know much about the development process, but as you said some bugs may be features or vice versa. Sometimes real bugs are fixed and peoples' code breaks. But keeping the bug around isn't an option. The next code breakage comes from making array slices consistently rvalues (the slice structure itself, not the data). It's not a new idea, like introducing immutable, just wasn't correctly implemented from the start. I don't know if this warrants a LTS release already. The problem will be obvious and easy to fix by introducing a temp variable to pass as lvalue into functions taking slices by ref. Or changing those functions to auto-ref.
- Release process and backwards compatibility Dicebot
- Re: Release process and backwards compatibility Marco Leise
- Re: Release process and backwards compatibility bearophile
- Re: Release process and backwards compatibilit... Daniel Murphy
- Re: Release process and backwards compatibility deadalnix
- Re: Release process and backwards compatibilit... Jesse Phillips
- Re: Release process and backwards compatib... deadalnix
- Re: Release process and backwards com... Jesse Phillips
- Re: Release process and backwards... deadalnix
- Re: Release process and backw... Jesse Phillips
- Re: Release process and backwards compatib... Dicebot
- Re: Release process and backwards compatibility Dicebot
