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
Suppose someone who studied modified RNAs want to work with this package. So they create a new BioSymbol type (and an Alphabet type for BioSequences work).
Does it make sense to have an interface with what is minimally expected to implement? I suppose one can get away with implementing very little.
The text was updated successfully, but these errors were encountered:
Perhaps we define a BioSymbols interface as a set of unsigned values, that have all the basic operations, plus a trait defining whether the values are one-hot encoded, to conform with an interface around compatibility etc.
To facilitate fast IO, we probably also want to have some sort of ASCII shortcuts, i.e. being able to construct UInt8 from your BioSymbol effectively when they can be represented as such.
Suppose someone who studied modified RNAs want to work with this package. So they create a new BioSymbol type (and an
Alphabet
type for BioSequences work).Does it make sense to have an interface with what is minimally expected to implement? I suppose one can get away with implementing very little.
The text was updated successfully, but these errors were encountered: