HackerTrans
TopNewTrendsCommentsPastAskShowJobs

gilnaa

no profile record

Submissions

How to FizzBuzz at 40GiB/S

codegolf.stackexchange.com
6 points·by gilnaa·5 jaar geleden·2 comments

comments

gilnaa
·3 jaar geleden·discuss
Like an onion
gilnaa
·4 jaar geleden·discuss
Polars is already not python
gilnaa
·4 jaar geleden·discuss
gilnaa
·4 jaar geleden·discuss
EDITOR=true is clever! Git has --no-edit as well, btw
gilnaa
·4 jaar geleden·discuss
Panics _can_ sometimes conceptually share the same implementation as exceptions, but given that their usage is not the same, and the fact that the ecosystem doesn't use panics as exceptions, it's a bit of stretch saying they're "functionally" the same.

A bit like saying trains and chairs are functionally the same since they both can have wheels; when there's the crucial difference that chairs don't go choo-choo.
gilnaa
·4 jaar geleden·discuss
Isn't this why Windows have MOV EDI, EDI at the start of a function? https://devblogs.microsoft.com/oldnewthing/20110921-00/?p=95...
gilnaa
·4 jaar geleden·discuss
"I want X" "Here's Y" "Yeah no"
gilnaa
·4 jaar geleden·discuss
Not to mention that it didn't even get into C++
gilnaa
·4 jaar geleden·discuss
You put #[non_exhaustive] on a enum in Rust to force users matching on it to handle an "else"/"default" case, so that you can add more variants to this enum in the future without breaking their code.

It doesn't mean that the enum itself is non exhaustive: at any point in time when enum is defined, it defines all of its variants and any other value is still UB.
gilnaa
·4 jaar geleden·discuss
It's not that it is unstable as much as it is needlessly painful to work with.
gilnaa
·5 jaar geleden·discuss
56GiB/s*
gilnaa
·5 jaar geleden·discuss
a tool doesn't have to be a clean room implementation to be useful