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
Currently, Df uses its own type Data, which is isomorphic to Maybe. This is very inconvenient, because we need convert between these types via Df.dataToMaybe and Df.maybeToData every time we need a function that specifically works on Maybe.
The original motivation for this design choice was that Maybe is lazy, but that does not seem to be a problem anymore. Moreover, other protocols such as Axi4Stream and PacketStream also use Maybe to indicate validity.
Currently,
Df
uses its own typeData
, which is isomorphic toMaybe
. This is very inconvenient, because we need convert between these types viaDf.dataToMaybe
andDf.maybeToData
every time we need a function that specifically works onMaybe
.The original motivation for this design choice was that
Maybe
is lazy, but that does not seem to be a problem anymore. Moreover, other protocols such asAxi4Stream
andPacketStream
also useMaybe
to indicate validity.We can also use https://hackage.haskell.org/package/strict-0.5.1/docs/Data-Strict-Maybe.html, but that does require an extra dependency.
The text was updated successfully, but these errors were encountered: