Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
CUViper
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
CUViper
5y ago
I had the pleasure of living with one -- my dad ran The Bailey Information Exchange in Colorado. We had a satellite feed and a few lines for folks to dial into. I would get on a local terminal to play Legend of the Red Dragon and TradeWars,
32.
▲
by
CUViper
5y ago
It's not actually shifting a char, because integer promotion happens first. https://github.com/glfw/glfw/pull/1986#issuecomment-95578417...
33.
▲
by
CUViper
5y ago
Or a magnetized needle, or a butterfly... https://xkcd.com/378/
34.
▲
by
CUViper
5y ago
That change came from the GCC steering committee, not the FSF.
35.
▲
by
CUViper
5y ago
The implementation of `fs::copy` uses `copy_file_range` on Linux, which does allow reflink optimizations.
36.
▲
by
CUViper
5y ago
You can't directly re-assign those developers, but you can try to influence their decisions. It's not only about the current developers either, but also potential new contributors that may be considering either project.
37.
▲
by
CUViper
6y ago
That's a funny example, because Rust's `String` does implement `Add` as concatenation! Many think this was a mistake though. https://doc.rust-lang.org/std/string/struct.String.html#impl...
38.
▲
by
CUViper
6y ago
It would be kind of amusing if this shortened code by re-rolling an unrolled loop.
39.
▲
by
CUViper
6y ago
There's a working group for MIR optimization: https://rust-lang.github.io/compiler-team/working-groups/mir...
40.
▲
by
CUViper
6y ago
On the range, the surrogates are actually 10 bits, 1024 possible values. The high surrogate is encoded in 0xD800-0xDBFF, and low in 0xDC00-0xDFFF.
41.
▲
by
CUViper
6y ago
Glibc malloc also limits the maximum according to ptrdiff_t, which is effectively the same as Rust isize.
42.
▲
by
CUViper
6y ago
I do it with a renamed `.git` and a bash alias `githome` that points `git` to the right place. This way it doesn't look like my home is a repo in normal use.
43.
▲
by
CUViper
6y ago
You can also use "cmake --build <dir>" to build regardless of which generator was used.
44.
▲
by
CUViper
6y ago
The dependency goes hyper -> h2 -> indexmap -> hashbrown, and indexmap is built on hashbrown::raw::RawTable.
45.
▲
by
CUViper
6y ago
For discovery, you could readdir, verify no case-sensitive overlaps, then stat a filename with changed case. Maybe compare inodes and number of hard links too if the changed name does succeed.
46.
▲
by
CUViper
6y ago
I see both the old and new packages on mirrors.kernel.org: https://mirrors.edge.kernel.org/centos/8.2.2004/BaseOS/x86_6...
47.
▲
by
CUViper
6y ago
It's actually every 4 weeks now!
48.
▲
by
CUViper
6y ago
Perl 6 may be a contender, now so different that it's renamed to Raku.
49.
▲
by
CUViper
6y ago
There was a presentation of generative art at RustConf 2019: https://youtube.com/watch?v=Ho3xr4b60Zg
50.
▲
by
CUViper
7y ago
Even that `ud2` is only there because rustc sets the `TrapUnreachable` flag for LLVM. In older versions you would get nothing at all, so calling main would fall through to whatever was next in memory.
51.
▲
by
CUViper
7y ago
> The fact that Ternimal.app That typo has a nice program of its own: https://github.com/p-e-w/ternimal
52.
▲
by
CUViper
7y ago
There are some broad examples of that effect here: https://en.wikipedia.org/wiki/Speedup#Super-linear_speedup
53.
▲
by
CUViper
7y ago
You might need to cover openat too. I think newer glibc uses the openat(AT_FDCWD,...) syscall for all open calls.
54.
▲
by
CUViper
7y ago
Doesn't each wasm module get its own isolated memory? If so, then you could only shoot your own sensitive foot.
55.
▲
by
CUViper
7y ago
ref: https://en.wikipedia.org/wiki/Pern#Thread
56.
▲
by
CUViper
7y ago
If Rayon were in the standard library, we would never be able to make breaking changes, whereas in a crate we can possibly release a Rayon 2.0. For instance, we might want to make some low-level changes in the way iterators split their work
57.
▲
by
CUViper
7y ago
In other languages, nothing ensures that those safe abstractions are actually used in safe ways. You can keep a dangling reference to a C++ vector, but Rust will make sure your references are valid, and you can only escape that with raw poi
58.
▲
by
CUViper
7y ago
FWIW Roland McGrath, the original glibc author, also works at Google. But of course not every possible person will be involved here, no matter how relevant.
59.
▲
by
CUViper
7y ago
Where do you draw the line on answering questions as a witness, versus refusing to answer as a potential accused person?
60.
▲
by
CUViper
7y ago
You can make wrapping writes look contiguous by mapping the same memory twice, one after the other. This is done in slice-deque such that the entire buffer can be viewed as a contiguous slice, regardless of the start/end positions. ht
More ›