Re:Compiler Bug Causes Compiler Bug: How a 12-Year-Old G++ B...
by RealityVoid on Friday August 15, 2025 @04:06PM
(#44916777)
As opposed to being subject to interpretation of the truth, with the courts of varying quality. My point is... everything has error bars.
[ Parent
| on HN ]
Re:Compiler Bug Causes Compiler Bug: How a 12-Year-Old G++ B...
by eightysixfour on Friday August 15, 2025 @07:34PM
(#44918496)
It must. Things that interact with the real world need slack.
Re:Compiler Bug Causes Compiler Bug: How a 12-Year-Old G++ B...
by sealeck on Friday August 15, 2025 @11:01PM
(#44919736)
> with the courts of varying quality
You can usually pick the jurisdiction (e.g. many contracts are under jurisdiction of England & Wales/Switzerland/Singapore despite neither party being based there, or doing business there).
I think in general judges are quite considered, and the answers you get from courts tend to make quite a lot of sense, especially if you are aware of general legal principles and precedent.
Re:Compiler Bug Causes Compiler Bug: How a 12-Year-Old G++ B...
by josefx on Saturday August 16, 2025 @04:47AM
(#44921492)
You are still subject to courts if you use smart contracts, they change literally nothing about that.
Re:Compiler Bug Causes Compiler Bug: How a 12-Year-Old G++ B...
by saghm on Saturday August 16, 2025 @04:54PM
(#44926853)
The reliance on context and human intervention in our current system is a feature, not a bug. That's my entire point; if you get rid of that, you're introducing a lot of issues, and if you don't, you're throwing out a system with literal centuries of stress-testing where the flaws are legitimate but well understood to switch to one with literally no evidence to suggest that it's better.