3 ms·
It cites an example from 2024 so the text has definitely been updated since 2022.
by tokai 1y ago
It cites an example from 2024 so the text has definitely been updated since 2022.
- dang 1y agoUsually when an article is substantively the same but has been updated, we use the original year. I've put 2022 in the title now. The previous HN thread: Correctness and composability bugs in the Julia ecosystem - https://news.ycombinator.com/item?id=31396861 https://news.ycombinator.com/item?id=31396861 - May 2022 (407 comments) Edit: since there are (again? I seem to remember this last time) complaints about the title being a bit too baity, I've pilfered that previous title for this thread as well
- deleted 1y ago[deleted]
- cs702 1y ago@dang, thank you for doing that. When I posted the OP, I considered changing the title, but decided not to editorialize it, per the guidelines.
- Alexander-Barth 1y agoThe incorrect example of julia's documentation was fixed 2021: https://github.com/JuliaLang/julia/commit/f31ef767ef9cb0eb1de04d23e2e9e1ac765869b3 https://github.com/JuliaLang/julia/commit/f31ef767ef9cb0eb1d... As an experiment, I would be interested to see if somebody would make a 1-based python list-like data structure (or a 0-based R array), to check how many 3rd party (or standard library) function would no longer work.