erasure

Does that mean that the compiler is doing erasure for generics coming in from Objective C, inserting runtime casts where needed, but then doing full reification on swift code?

Would love your thoughts and feedback, and to hear of what you do with this erasure coding library.

One of the well-known effects of colonialism (both in India and elsewhere) is the erasure of this influence.

Calling for its eradication is to call for the erasure of a fundamental aspect of human cognition.

This is the team that brought generics to.net; without them they'd probably have Java's lameass erasure model.

This erasure code is not at all optimal; it only serves to teach the basics of how one could work.

In short, when you get to the point in implementing a language where you can do type erasure, you're golden because it usually means you have things nailed down.

I believe the difference is that in this case, RS is being used as an erasure code (which means, you either have the data or you don't; the drive has either failed or it hasn't).

If you compete, you’ll end up learning erasure coding, Diffie-Hellman key exchange, write a small programming language, etc.

Generic types in C are typically done through type erasure or an intrusive type.

Donut - is a distributed erasure coded backend format, designed specifically for immutable data.

Both protobuf and Thrift are designed exclusively around simple static type-checking with type-erasure.

Type erasure is a complex solution to an easy problem, done purely out of laziness and a broken sense of what "backwards compatible" should mean.

Bizarre that this fellow grimaces at "type erasure".

At the end of the presentation, they mention rotated reed-soloman array codes, which led me to another paper Plank worked on: "Rethinking Erasure Codes for Cloud File Systems: Minimizing I/O for Recovery and Degraded Reads" which was very interesting as well.

Erasure-coded comments distributed across the huge number of abandoned Wordpress blogs and phpBB forums that are out there.