Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
System.Sequence: inconsistency in 'number' field #45
The 'number' field contains the last used value of the sequence, which is certainly useful for applicative
But this isn't true right after creation: it is in that case the first value that will be returned, unless it is 0 in which case the starting value is 1.
The problem is see here is that applicative code has no way to know the correct meaning.
A cleaner way of doing would be to use two fields: