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
Since version 9.5.3 fastutil provides a variant named fastutil-core, which only contains the important types and is therefore only about 6MB in size instead of 22MB.
Would it be possible to require only fastutil-core for tablesaw?
For tablesaw-core depending only on fastutil-core leads to compiler errors, but from a coarse look (and without in depth knowledge) it looks in general doable. Only the types listed below would need a replacement.
But these types are used in tablesaw's API and I don't know what your policy respectively backwards compatibility is and if it would be feasible for you to break those APIs.
Since version 9.5.3
fastutil
provides a variant namedfastutil-core
, which only contains the important types and is therefore only about 6MB in size instead of 22MB.Would it be possible to require only
fastutil-core
for tablesaw?For
tablesaw-core
depending only onfastutil-core
leads to compiler errors, but from a coarse look (and without in depth knowledge) it looks in general doable. Only the types listed below would need a replacement.But these types are used in tablesaw's API and I don't know what your policy respectively backwards compatibility is and if it would be feasible for you to break those APIs.
But since ByteArrayList and BooleanSet
Relates to
The text was updated successfully, but these errors were encountered: