Java

1388 readers

1 users here now

For discussing Java, the JVM, languages that run on the JVM, and other related technologies.

founded 1 year ago

MODERATORS

Ategon

JackbyDev

thtroyer

Erasure: how we got the generics we have, or how I learned to stop worrying and love erasure (cr.openjdk.org)

submitted 1 year ago by JackbyDev to c/java

15 comments fedilink hide all child comments

A great read for folks wondering why Java uses type erasure instead of "reified" generics. For the unaware, that means that a List<Integer> is a List<Object> at runtime. I had always wondered about it and why they didn't take the alternative route. For context, C# does have reified types so the actual type parameter is available at runtime.

I personally love reading in depth discussions about counter intuitive engineering decisions like this.

you are viewing a single comment's thread
view the rest of the comments

[–] JackbyDev 2 points 1 year ago* (last edited 1 year ago) (1 children)

As a heads up, idk if it is just the Jerboa app or Lemmy but I your type params on Sensor were being interpreted as HTML tags and not rendered. The ones in the first paragraph are fine though.

Can we use raw HTML?

Edit: looks like it just gets blocked and not read.

Edit 2: Looks like Jerboa and the browser display this differently actually lol

[–] [email protected] 1 points 1 year ago (1 children)

Funnily enough, I typed that one in the Jerboa app, but yeah, it's not rendering for me either. 🙃

[–] JackbyDev 2 points 1 year ago

I opened a GitHub issue. I think it's probably just a config thing as they are both based on the CommonMark spec. Or maybe a nug with one of the markdown libs themselves.