5 ms·
Your answer doesn't answer the question. You ask what type erasure is and then answer with some very specific information on Java's generics. Nothing in your qu
by Jtsummers 8y ago
Your answer doesn't answer the question. You ask what type erasure is and then answer with some very specific information on Java's generics. Nothing in your question indicates that it's about Java or generics.
> Maybe using it for precise definitions is the wrong way, as that might be more like remembering 20 things in a row.
This is exactly what it can be like. The 20 rules from SuperMemo are really useful for trying to formulate and transform the cards.
https://www.supermemo.com/en/articles/20rules https://www.supermemo.com/en/articles/20rules
- Noumenon72 8y agoIt's always odd how failing at most things leads me to ask "how am I doing this wrong?" and overcome, but I never asked this about Anki. Thanks for the link. I was not aware till this moment that type erasure was something that C++ also has. I thought it was a specific gotcha for Java like the whole "no == for Strings" thing. In that context, I've only seen it connected to generics.