Live data from Hacker News

Scala 3.0

github.com

1–10 of 292 posts

Re: Scala 3.0

#4
I get paid to write TypeScript, it has come a long way to a relatively enjoyable experience compared to how expressive i feel with Scala. Looking forward to giving Scala 3 a spin to learn whats new

Re: Scala 3.0

#5
post #2

I wonder why it's not on the official site [1]. [1] https://www.scala-lang.org/

they just created a tag, i guess they are preparing the press release :)

Re: Scala 3.0

#6
post #4

I get paid to write TypeScript, it has come a long way to a relatively enjoyable experience compared to how expressive i feel with Scala. Looking forward to giving Scala 3 a spin to learn whats new

I was looking at dotty/scala 3 earlier in the year and I was quite surprised to see familiar friends from Typescript in the form of literal types and union types.

val scala: "Scala" = "Scala"

const typescript: "Typescript" = "Typescript"

"Scala" | "Typescript"

Re: Scala 3.0

#10
post #6
post #4

I get paid to write TypeScript, it has come a long way to a relatively enjoyable experience compared to how expressive i feel with Scala. Looking forward to giving Scala 3 a spin to learn whats new

I was looking at dotty/scala 3 earlier in the year and I was quite surprised to see familiar friends from Typescript in the form of literal types and union types. val scala: "Scala" = "Scala" const typescript: "Typescript" = "Typescript" "Scala" | "Typescript"

This creates two types with quotes in their type names, and then creates a union type of the two? Then the compiler needs to determine if the token's context requires a type or a value, and disambiguate accordingly?

In the example above, the created type "Scala" is distinct from a type Scala, correct?

I did some quick poking around for Scala literal types, but I found stuff like https://github.com/jeremyrsmith/literal-types , which don't look like the example above.

Post reply on HN