Your concerns should be addressed now, also everything is backported to 1.3.x.
@all I'd really like to hear some more opinions on these changes. I want to roll releases sooner than later (likely in the coming days) Thanks Markus Am 3. November 2026 21:24:59 MEZ schrieb Romain Manni-Bucau <[email protected]>: >If I get right the intent it should break 0 apps so think it is just a >patch increase, that said there are 2 things I'm not fan and didn't get >time yet to check in details: > >1. > int numberLength = 1; // the first digit or minus sign is already >in the buffer > if (numberLength > maxNumberLength) { > throw tmn(); > } > >-> think it should fail in the static init part or setter of the bound if >max number length is too low > >2. >also why nextNumberLength is called for any char (you know upfront the >margin you have so you can read by bulk without check every char if you >reached the limit > >For the rest while setting the system propery enable to get back to the >prevous behavior it is great but the perf impact can need some refinement >for number heavy payloads. > >Romain Manni-Bucau >@rmannibucau <https://x.com/rmannibucau> | .NET Blog ><https://dotnetbirdie.github.io/> | Blog <https://rmannibucau.github.io/> | Old >Blog <http://rmannibucau.wordpress.com> | Github ><https://github.com/rmannibucau> | LinkedIn ><https://www.linkedin.com/in/rmannibucau> | Book ><https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064> >Javaccino <https://javaccino.dev/> founder (Java/.NET service - contact via >linkedin) > > >Le mar. 3 nov. 2026 à 20:52, Markus Jung via dev <[email protected]> a >écrit : > >> Hey all, >> >> I did some improvements lately which changes a bit of default behavior >> (look at 80b26a0 and 55c3fb7 for details). >> >> Do you think we should bump to 2.3.0/1.4.0 over this? Theoretically this >> is changing behavior and beyond a simple patch, in practice I think the >> defaults are sane enough to not have any users hit them. WDYT? >> >> >> Thanks >> >> Markus
