state of the branch sealed-and-record ?

[Brian Goetz]

There will temporarily not be a branch that merges these; once we finish staging records for review, we’ll re-parent a sealed type branch on it.  Or, you can use an older revision on the rcords-and-sealed branch in the meantime.

> On Oct 20, 2019, at 10:21 AM, Mark Raynsford <org.openjdk at io7m.com> wrote:
> 
> On 2019-10-20T10:08:52 -0400
> Vicente Romero <vicente.romero at oracle.com> wrote:
> 
>> Hi Remi,
>> 
>> A new branch named `records` was created which contains only the records 
>> code. The former records-and-sealed branch should contain only the 
>> sealed code but as it depends on the record branch, from the user 
>> perspective will continue to have the code of both projects. It could 
>> happen though that the automatic merge can't figure out what to do at 
>> some point an as a result the records-and-sealed branch could be broken 
>> we will try to keep it working but it could fall off the cliff from time 
>> to time,
> 
> Hello!
> 
> I'm about to try doing an experimental rewrite of a small documentation
> language compiler I have using both sealed types and records. To
> clarify: Which branch should I be using?
> 
> -- 
> Mark Raynsford | http://www.io7m.com
>