News for hackers. Stuff that matters.

JeromeBonnet

My understanding is that the detection order follows the underlying phenomena: first the neutron stars fell towards each other, producing gravitational waves, and only then did the stars collide, producing electromagnetic waves.
Re:Rapidstring: Maybe the fastest string library ever on Wednesday August 01, 2018 @05:39AM (#17660969)
It is a trade off. I see the length limit is 23 for SSO-23, but it could have been arbitrarily larger. What is the basis for the determination of those magic length limit targets?
Re:Rapidstring: Maybe the fastest string library ever on Wednesday August 01, 2018 @04:57AM (#17660734)
> Why would you store the size and capacity as part of the buffer?

To decrease the memory footprint of your small strings. It can see how some uses cases where a large proportion of strings are very small would benefit from it.

I was just curious to know if that design decision was based on analysis of a real use case, or if it was due to a compatibility issue or something.

Re:Rapidstring: Maybe the fastest string library ever on Wednesday August 01, 2018 @04:06AM (#17660458)
Hi, John! Why did you chose to store 'size' and 'capacity' in the 'rs_heap' struct instead of at the beginning of the heap-allocated buffer pointed to by 'buffer'? Did you find it was preferable to have a larger 'rs_heap'?