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
We've been reexporting Stdlib, which is great for things like easily using ThCategory in Catlab. However, there are a lot of things in Stdlib and they are likely to be more 'toy implementation' than the analogous thing we want in Catlab. For example, FinSetC is a great name for the category of finite sets and functions, but in Catlab it would be better to define this with the FinSet machinery that is defined there (the version in GATlab.Stdlib is a toy version of SkelFinSet). In general, there have been many name collisions (e.g. op) that seem harder to deal with than occasional explicit using GATlab.Stdlib: ThCategory, so I think it would be best to not reexport Stdlib.
For reference, here are all the names included in Stdlib:
We've been reexporting Stdlib, which is great for things like easily using
ThCategory
in Catlab. However, there are a lot of things in Stdlib and they are likely to be more 'toy implementation' than the analogous thing we want in Catlab. For example,FinSetC
is a great name for the category of finite sets and functions, but in Catlab it would be better to define this with theFinSet
machinery that is defined there (the version in GATlab.Stdlib is a toy version of SkelFinSet). In general, there have been many name collisions (e.g.op
) that seem harder to deal with than occasional explicitusing GATlab.Stdlib: ThCategory
, so I think it would be best to not reexport Stdlib.For reference, here are all the names included in Stdlib:
The text was updated successfully, but these errors were encountered: