segmented

In Rust we use the system libc with segmented stacks, and we call C code by switching stacks.

The world is not segmented into feature phones and smartphones.

So the basic problem is that this benchmark is simply tuned for segmented stacks.

In Spain, some people take a quick 30-minute nap after lunch, but I wouldn't call that sleeping in segmented blocks.

An implementation that does not use segmented stacks will do worse on this benchmark.

It is segmented into one market "I want to use a networked mobile app to get laid or get cash.

I'd rather someone tries segmented stacks and determines it isn't a good fit than to just discard it on a comment from something someone said.

Imagine how easy it would be to have C call Go code if Go didn't have its own threading and segmented stacks; simply push the arguments and call/jmp.

Other than that, there are no studies of importance here, nothing that confirms concretely that this kind of segmented sleep is effective for humans.

The figures are really nice!One observation: training a neural net to classify segmented characters is probably overkill.

* Real mode: the "nobody's ever going to need more than 64k of memory" mode in which 80's DOS programs expect to run, includes segmented memory and IN/OUT I/O instruction access.

The design->planning->building segmented workflow will always exist, as it has in all engineering disciplines since the dawn of human civilization.

On 32-bit, however, segmented stacks do theoretically allow many many many more concurrent tasks than you'd achieve merely with multithreading.

That was a deliberate choice, because not having segmented stacks makes many much more important things far faster, such as calling into C and performing tight sequential computations without thrashing on stack boundaries or using a garbage collector to move stacks around and rewrite all the pointers.

Go was not designed for 32 bit, segmented stacks are great because of reasons that have nothing to have with address space addressability, in fact there are C implementations that use segmented stacks, segmented stacks do not preclude using the system libc, the reasons for bypassing libc were completely different, and calling C code from Go works just fine.