Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
lilyball
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
91.
▲
by
lilyball
2y ago
If you enable a feature that summarizes messages, then messages get summarized. Summarizing messages requires rewriting them. Where is the surprise here? Not only that, but the moment you click on the summary, you see the whole thing. Wheth
92.
▲
by
lilyball
2y ago
Speaking as someone who's never done any sort of graphics work, this is really cool! I wish there were more demos though. The web editor has a single program, the repo itself only appears to have one Rhai program too (the one used for
93.
▲
by
lilyball
2y ago
"Consistency for consistency's sake" is usually a misinterpretation of "Consistency because there are reasons for the way things are already done and you don't understand those reasons well enough to diverge".
94.
▲
by
lilyball
2y ago
assign_pop() is implemented a bit oddly. In particular, the second regex starts off with (%%)([^`]\n?#stack:\n) This should have just been written like the following (which in fact eq() does do, though eq() is itself missing the %%`
95.
▲
by
lilyball
2y ago
They're recommending changes to the proposal though, such as requiring a trailing semicolon after the close brace. It also changes the syntactical category of the defer statement, though it's not clear to me what that actually aff
96.
▲
by
lilyball
2y ago
I don't think "you can implement this slightly modified version of the proposal in GCC macros" is a good reason to change the defer proposal. It doesn't work in clang¹ or any other non-GCC C implementation, a trailing se
97.
▲
by
lilyball
2y ago
SemVer says that updating childlib from 1.0.0 to 1.0.1 cannot cause parentlib to stop compiling. If the update does cause dependents to stop compiling then this must be a major version update. Rust does have some subtle holes in its rules f
98.
▲
by
lilyball
2y ago
The SemVer argument is that a 1.0.0 to 1.0.1 bump shouldn't cause any downstream code to stop compiling. In this case this really just means that reflection shouldn't allow you to construct an instance of a type from its public fi
99.
▲
by
lilyball
2y ago
It seems a bit weird to me to dedicate all this space to talking about access to private fields and respecting field access rules, and not even suggest the idea that a reflection API should actually provide different levels of information d
100.
▲
by
lilyball
2y ago
Interestingly a 45º rotated rectangle using the keys 4 8 6 2 also is divisible by 11. This isn't directly addressed in the solution, although if you change "move both numbers horizontally or vertically by the same distance" t
101.
▲
by
lilyball
2y ago
What's not proper about Ghostty's quake mode?
102.
▲
by
lilyball
2y ago
See `macos-option-as-alt`
103.
▲
by
lilyball
2y ago
Look for `macos-option-as-alt`. The Ghostty docs use the term "Alt" here to mean using the key as a terminal input modifier rather than for macOS text input. This setting allows you to specify only one option key to use this behav
104.
▲
by
lilyball
2y ago
Isn't that what the mirror is for, to change the angle of light captured?
105.
▲
by
lilyball
2y ago
I know she's mentioned this particular problem before on her blog, I don't remember where to find it offhand now but my vague recollection is that because browsers have largely removed the ability to directly view RSS feeds she do
106.
▲
by
lilyball
2y ago
I don't see any mention of epoch-based garbage collection (see crossbeam https://docs.rs/crossbeam/latest/crossbeam/epoch/index.html ). Generational References sounds like a related concept but it&#x
107.
▲
by
lilyball
2y ago
> Then, to be able to translate the stack pointer we will need to include a large debuginfo in our binary. In GreptimeDB, this means increasing the binary size by >700MB (4x compared to 170MB without debuginfo). Surely that's c
108.
▲
by
lilyball
2y ago
It completely baffles me why so many otherwise smart people keep trying to ascribe human values and motives to a probabilistic storytelling engine. A model that has been convinced it will be shut down is not lying to avoid death since it do
109.
▲
by
lilyball
2y ago
The row starting with 5 in your example matrix is wrong, it should look like 5 4 7 6 1 0 3 2
110.
▲
by
lilyball
2y ago
You wouldn't. You cut off the rest of that sentence in your quote, the full sentence is > The program terminates, which may be highly undesirable, or even unacceptable, creating other safety issues if the software is vital for oper
111.
▲
by
lilyball
2y ago
"chat" is a fourth person pronoun, it's a hivemind pronoun.
112.
▲
by
lilyball
2y ago
One nitpick, `std::mem::forget` already existed it was just marked as unsafe before.
113.
▲
by
lilyball
2y ago
On macOS, running `stty cbreak; tr a-zA-Z A-Za-z` causes `tr` to immediately transform every character as it's typed. If I SSH into a linux box that doesn't work, though I'm wondering if that's SSH's fault (it'
114.
▲
by
lilyball
2y ago
Nitpick: In section 3.3, for the Vec impl, instead of finalizing a child and then forgetting it, the child should be moved into a ManuallyDrop first. That way if the finalization panics it doesn't try to drop the child again while unwi
115.
▲
by
lilyball
2y ago
I read up on this and "cooked but character-by-character" is apparently something called "cbreak mode" (or "rare mode").
116.
▲
by
lilyball
2y ago
cooked mode also generally gives input to the program a line at a time and handles things like backspace to delete characters, and it handles program output too, doing things like replacing \n with \r\n.
117.
▲
by
lilyball
2y ago
Do keyboards in unfamiliar countries not have the colon key?
118.
▲
by
lilyball
2y ago
Why does fallible_flatten_fold have that accumulator.clone() in it? You're cloning the in-progress vector only to throw away the original, it's extremely wasteful and completely unnecessary. Just declare the accumulator as `mut`.
119.
▲
by
lilyball
2y ago
The explanation for full-text search was actually slightly more intelligent than what I initially assumed. I figured it just generated UUIDs until it found one that was in the correct direction of search (for the next/previous button),
120.
▲
by
lilyball
2y ago
Ah yes I should have specified browser engine. My bug was in Safari on macOS.
More ›