Closed twosatsmaxi closed 4 months ago
What would be the goal of splitting out the runestone types into a separate crate? I don't think it would particularly improve compile times, since without tests, the ordinals crate is only 1600 lines of code. Presumably most projects that use the ordinals
will have much heavier dependencies, so I don't think it would improve compile times much. I agree it would probably be slightly cleaner, but I think that's probably outweighed by the annoyance of having to remember to update more crates, and having more different places for code to live.
What would be the goal of splitting out the runestone types into a separate crate?
Just for better segregation, I feel that it's easier to segregate them now than later when rune related code grows (and it'll grow I think), refactoring it later would be a pain. But this makes sense only if we are planning to extract out rune related code (not just crate but eveything else) out or ord. I do agree that there is a cost to it in maintaining it inititaly, but this'll give an idea and will be a starting point to extract rune out of ord.
I think it's probably easier to split them when there's an actual problem that we want to solve. In general, I try not to anticipate problems too much, as long as they're not critical, since if you try to fix a problem you only might have in the future, it might never actually manifest.
runestone = "0.0.0"
but it's not maintained and it's not being used too in this repo?