slices

Ultimately, the problem is that for any given slice of humanity, there are significant other slices of humanity that the former find repugnant.

It's a measly 43 calories per slice, with me maxing out at 4 slices on my best days.

Any generics solution has to have fast runtime, because they need to replace the builtin parametric slices and maps.

Is the market really growing by 2 x PI x the width of one of their slices?

Standing by the table you would only actually be able to see tiny slices at a time.

It is very likely that, were there numbers for smaller slices at the top, the ratios would be astronomical.

Isn't that sort of like saying it's not worth using data structures other than maps and slices?

It doesn't support explicit freeing, but you can always reuse buffers and write your code to allocate slices within them.

Taxi drivers and politicians in Brazil are fighting Uber because they are losing slices of a pie that is deeply corrupted.

You're supposed to compare the area of these half circle shaped rotated slices easily?

Generics would codegen exactly the same way as slices and maps do now.

And they would be widely used, any good generics solution would have to replace maps and slices, and would permeate the standard library.

Will anybody ever "own" all the market slices Google currently plays in?

An analogy that might help morale about the reverse split: "Instead of each getting eight pizza slices (opening price $0.25, strike price $1), you each get one pie (opening price $2, strike price $8)."

Slices and maps are just built-in generics.