The code blocks break mobile viewport width. Surely it's better than wrapping, but the best solution is to use max-width and overflow-x: auto which makes them scrollable.
fanf2 122 days ago [-]
I prefer zooming for reading code. Horizontal scrolling divs are horrible.
Etheryte 122 days ago [-]
But then you still end up scrolling horizontally once you're zoomed in, no? What's the difference?
122 days ago [-]
fanf2 122 days ago [-]
I can zoom out.
aqrit 122 days ago [-]
Why not use regular rejection sampling when `limit` is known at compile-time.
Does fastrange[1] have fewer rejections due to any excess random bits[2]?
Fastrange is slightly biased because, as Steve Canon observes in that Swift PR, it is just Knuth’s multiplicative reduction. The point of this post is that it’s possible to simplify Lemire’s nearly-divisionless debiasing when the limit is known at compile time.
Lemire’s algorithm rejects the fewest possible samples from the random number generator, so it’s generally the fastest. The multiplication costs very little compared to the RNG.
egberts1 121 days ago [-]
sounds like random prime numbers to me.
rewqa 122 days ago [-]
[flagged]
Rendered at 08:11:59 GMT+0000 (UTC) with Wasmer Edge.
[1] https://github.com/lemire/fastrange
[2] https://github.com/swiftlang/swift/pull/39143
Fastrange is slightly biased because, as Steve Canon observes in that Swift PR, it is just Knuth’s multiplicative reduction. The point of this post is that it’s possible to simplify Lemire’s nearly-divisionless debiasing when the limit is known at compile time.
I previously experimented with really-divisionless debiasing but I was underwhelmed with the results https://dotat.at/@/2022-04-20-really-divisionless.html
I was thinking naive: mask off unwanted bits then reject any value above the limit.
It would seem like https://c-faq.com/lib/randrange.html would also move the multiply --or divide by constant-- out of the loop.