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
IMO the package suffers from "kitchen sink syndrome": many of the exported functions could rather live in separate packages.
I share the belief that an interface package providing something like elconvert is necessary in the ecosystem, however the other functions would ideally be stripped out of this package, because not everyone will need them.
The text was updated successfully, but these errors were encountered:
I understand what you mean. However last time when I tried to register a micropackage, I got rejected and I link their reasons here: JuliaRegistries/General#102561 (comment)
I'll consider having dedicated packages for the other functions until their implementations become big.
IMO the package suffers from "kitchen sink syndrome": many of the exported functions could rather live in separate packages.
I share the belief that an interface package providing something like
elconvert
is necessary in the ecosystem, however the other functions would ideally be stripped out of this package, because not everyone will need them.The text was updated successfully, but these errors were encountered: