You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One comment that came up during the Connect meeting that I thought was really interesting was the idea of conventions for a reserved array namespace in SeqCol. The idea being that if future properties are identified that would become part of the specification, it would provide a mechanism for adding those properties without potentially colliding with implementation-defined array names. An idea proposed was that a case-sensitive convention could be used for this purpose, which may have implications for #33.
The text was updated successfully, but these errors were encountered:
One comment that came up during the Connect meeting that I thought was really interesting was the idea of conventions for a reserved array namespace in SeqCol. The idea being that if future properties are identified that would become part of the specification, it would provide a mechanism for adding those properties without potentially colliding with implementation-defined array names. An idea proposed was that a case-sensitive convention could be used for this purpose, which may have implications for #33.
The text was updated successfully, but these errors were encountered: