feat: named unions

[aljazerzen]

Support for parsing and codegen of:

type Status=(Paid=()||Unpaid= float ||{reason = text, cancelled_at = timestamp}||)

As we don't have any code for interaction with this, this does not change the behavior in any way, so I'm not adding a changelog.

[vanillajonathan]

Seems related to #2930. This is cool but the syntax is quite jarring. I would have expected something much simpler and more akin to what is available in other languages.

[max-sixty]

This is cool but the syntax is quite jarring. I

In a way these are similar to Enums, since they're Sum Types. Though I don't see the immediate need to build that feature now. (and because we're early in this feature, and it is mostly internal, we shouldn't prioritize aesthetics highly)

One small change that might make it look better is to put the binary operators at the beginning of the next line. The standards for this changed to this in python a few years ago, which made pipelines of binary operators easier to read.

[aljazerzen]

Like this?

 type Status = (
|| Paid = ()
|| Unpaid = float
|| {reason = text, cancelled_at = timestamp}
)

We don't allow leading ||, so this won't work. If you think about || as a comma, it makes sense that they are at the end of the line.

But again, these are just aesthetics.

[max-sixty]

Almost, but there's no leading || (so the string of characters is still the same as the prior version)

 type Status = (
- || Paid = ()+ Paid = ()
|| Unpaid = float
|| {reason = text, cancelled_at = timestamp}
)

[aljazerzen]

Support for parsing and codegen of:

type Status=(Paid=()||Unpaid= float ||{reason = text, cancelled_at = timestamp}||)

As we don't have any code for interaction with this, this does not change the behavior in any way, so I'm not adding a changelog.

[vanillajonathan]

Seems related to #2930. This is cool but the syntax is quite jarring. I would have expected something much simpler and more akin to what is available in other languages.

[max-sixty]

This is cool but the syntax is quite jarring. I

In a way these are similar to Enums, since they're Sum Types. Though I don't see the immediate need to build that feature now. (and because we're early in this feature, and it is mostly internal, we shouldn't prioritize aesthetics highly)

One small change that might make it look better is to put the binary operators at the beginning of the next line. The standards for this changed to this in python a few years ago, which made pipelines of binary operators easier to read.

[aljazerzen]

Like this?

 type Status = (
|| Paid = ()
|| Unpaid = float
|| {reason = text, cancelled_at = timestamp}
)

We don't allow leading ||, so this won't work. If you think about || as a comma, it makes sense that they are at the end of the line.

But again, these are just aesthetics.

[max-sixty]

Almost, but there's no leading || (so the string of characters is still the same as the prior version)

 type Status = (
- || Paid = ()+ Paid = ()
|| Unpaid = float
|| {reason = text, cancelled_at = timestamp}
)

[aljazerzen]

Support for parsing and codegen of:

type Status=(Paid=()||Unpaid= float ||{reason = text, cancelled_at = timestamp}||)

As we don't have any code for interaction with this, this does not change the behavior in any way, so I'm not adding a changelog.

[vanillajonathan]

Seems related to #2930. This is cool but the syntax is quite jarring. I would have expected something much simpler and more akin to what is available in other languages.

[max-sixty]

This is cool but the syntax is quite jarring. I

In a way these are similar to Enums, since they're Sum Types. Though I don't see the immediate need to build that feature now. (and because we're early in this feature, and it is mostly internal, we shouldn't prioritize aesthetics highly)

One small change that might make it look better is to put the binary operators at the beginning of the next line. The standards for this changed to this in python a few years ago, which made pipelines of binary operators easier to read.

[aljazerzen]

Like this?

 type Status = (
|| Paid = ()
|| Unpaid = float
|| {reason = text, cancelled_at = timestamp}
)

We don't allow leading ||, so this won't work. If you think about || as a comma, it makes sense that they are at the end of the line.

But again, these are just aesthetics.

[max-sixty]

Almost, but there's no leading || (so the string of characters is still the same as the prior version)

 type Status = (
- || Paid = ()+ Paid = ()
|| Unpaid = float
|| {reason = text, cancelled_at = timestamp}
)

[aljazerzen]

Support for parsing and codegen of:

type Status=(Paid=()||Unpaid= float ||{reason = text, cancelled_at = timestamp}||)

As we don't have any code for interaction with this, this does not change the behavior in any way, so I'm not adding a changelog.

[vanillajonathan]

Seems related to #2930. This is cool but the syntax is quite jarring. I would have expected something much simpler and more akin to what is available in other languages.

[max-sixty]

This is cool but the syntax is quite jarring. I

In a way these are similar to Enums, since they're Sum Types. Though I don't see the immediate need to build that feature now. (and because we're early in this feature, and it is mostly internal, we shouldn't prioritize aesthetics highly)

One small change that might make it look better is to put the binary operators at the beginning of the next line. The standards for this changed to this in python a few years ago, which made pipelines of binary operators easier to read.

[aljazerzen]

Like this?

 type Status = (
|| Paid = ()
|| Unpaid = float
|| {reason = text, cancelled_at = timestamp}
)

We don't allow leading ||, so this won't work. If you think about || as a comma, it makes sense that they are at the end of the line.

But again, these are just aesthetics.

[max-sixty]

Almost, but there's no leading || (so the string of characters is still the same as the prior version)

 type Status = (
- || Paid = ()+ Paid = ()
|| Unpaid = float
|| {reason = text, cancelled_at = timestamp}
)

[aljazerzen]

Support for parsing and codegen of:

type Status=(Paid=()||Unpaid= float ||{reason = text, cancelled_at = timestamp}||)

As we don't have any code for interaction with this, this does not change the behavior in any way, so I'm not adding a changelog.

[vanillajonathan]

Seems related to #2930. This is cool but the syntax is quite jarring. I would have expected something much simpler and more akin to what is available in other languages.

[max-sixty]

This is cool but the syntax is quite jarring. I

In a way these are similar to Enums, since they're Sum Types. Though I don't see the immediate need to build that feature now. (and because we're early in this feature, and it is mostly internal, we shouldn't prioritize aesthetics highly)

One small change that might make it look better is to put the binary operators at the beginning of the next line. The standards for this changed to this in python a few years ago, which made pipelines of binary operators easier to read.

[aljazerzen]

Like this?

 type Status = (
|| Paid = ()
|| Unpaid = float
|| {reason = text, cancelled_at = timestamp}
)

We don't allow leading ||, so this won't work. If you think about || as a comma, it makes sense that they are at the end of the line.

But again, these are just aesthetics.

[max-sixty]

Almost, but there's no leading || (so the string of characters is still the same as the prior version)

 type Status = (
- || Paid = ()+ Paid = ()
|| Unpaid = float
|| {reason = text, cancelled_at = timestamp}
)

[aljazerzen]

Support for parsing and codegen of:

type Status=(Paid=()||Unpaid= float ||{reason = text, cancelled_at = timestamp}||)

As we don't have any code for interaction with this, this does not change the behavior in any way, so I'm not adding a changelog.

[vanillajonathan]

Seems related to #2930. This is cool but the syntax is quite jarring. I would have expected something much simpler and more akin to what is available in other languages.

[max-sixty]

This is cool but the syntax is quite jarring. I

In a way these are similar to Enums, since they're Sum Types. Though I don't see the immediate need to build that feature now. (and because we're early in this feature, and it is mostly internal, we shouldn't prioritize aesthetics highly)

One small change that might make it look better is to put the binary operators at the beginning of the next line. The standards for this changed to this in python a few years ago, which made pipelines of binary operators easier to read.

[aljazerzen]

Like this?

 type Status = (
|| Paid = ()
|| Unpaid = float
|| {reason = text, cancelled_at = timestamp}
)

We don't allow leading ||, so this won't work. If you think about || as a comma, it makes sense that they are at the end of the line.

But again, these are just aesthetics.

[max-sixty]

Almost, but there's no leading || (so the string of characters is still the same as the prior version)

 type Status = (
- || Paid = ()+ Paid = ()
|| Unpaid = float
|| {reason = text, cancelled_at = timestamp}
)

[aljazerzen]

Support for parsing and codegen of:

type Status=(Paid=()||Unpaid= float ||{reason = text, cancelled_at = timestamp}||)

As we don't have any code for interaction with this, this does not change the behavior in any way, so I'm not adding a changelog.

[vanillajonathan]

Seems related to #2930. This is cool but the syntax is quite jarring. I would have expected something much simpler and more akin to what is available in other languages.

[max-sixty]

This is cool but the syntax is quite jarring. I

In a way these are similar to Enums, since they're Sum Types. Though I don't see the immediate need to build that feature now. (and because we're early in this feature, and it is mostly internal, we shouldn't prioritize aesthetics highly)

One small change that might make it look better is to put the binary operators at the beginning of the next line. The standards for this changed to this in python a few years ago, which made pipelines of binary operators easier to read.

[aljazerzen]

Like this?

 type Status = (
|| Paid = ()
|| Unpaid = float
|| {reason = text, cancelled_at = timestamp}
)

We don't allow leading ||, so this won't work. If you think about || as a comma, it makes sense that they are at the end of the line.

But again, these are just aesthetics.

[max-sixty]

Almost, but there's no leading || (so the string of characters is still the same as the prior version)

 type Status = (
- || Paid = ()+ Paid = ()
|| Unpaid = float
|| {reason = text, cancelled_at = timestamp}
)

[aljazerzen]

Support for parsing and codegen of:

type Status=(Paid=()||Unpaid= float ||{reason = text, cancelled_at = timestamp}||)

As we don't have any code for interaction with this, this does not change the behavior in any way, so I'm not adding a changelog.

[vanillajonathan]

Seems related to #2930. This is cool but the syntax is quite jarring. I would have expected something much simpler and more akin to what is available in other languages.

[max-sixty]

This is cool but the syntax is quite jarring. I

In a way these are similar to Enums, since they're Sum Types. Though I don't see the immediate need to build that feature now. (and because we're early in this feature, and it is mostly internal, we shouldn't prioritize aesthetics highly)

One small change that might make it look better is to put the binary operators at the beginning of the next line. The standards for this changed to this in python a few years ago, which made pipelines of binary operators easier to read.

[aljazerzen]

Like this?

 type Status = (
|| Paid = ()
|| Unpaid = float
|| {reason = text, cancelled_at = timestamp}
)

We don't allow leading ||, so this won't work. If you think about || as a comma, it makes sense that they are at the end of the line.

But again, these are just aesthetics.

[max-sixty]

Almost, but there's no leading || (so the string of characters is still the same as the prior version)

 type Status = (
- || Paid = ()+ Paid = ()
|| Unpaid = float
|| {reason = text, cancelled_at = timestamp}
)