actually, that makes no sense. Forget it ;P
turned out I needed a Set instead of an Interval, though (for subtraction and intersection)
I turn it into a list of terms and serialize that
And then I decode in the same way
If there was an implementation using this as the data type (currently I don't think spire's polynomial is implemente like this), then that would be really efficient to serialize. It would just be an array with each element being the coefficient (with zeros for those powers that are missing).
So essentially no need to serialize at all, as the scala representation could match the binary representation.
It would also allow really efficient vectorized computation.
It would also allow really efficient vectorized computation.
apparently the
Eq instance throws exceptions when comparing
Slightly off topic, but this is the right kind of crowd for this type of stuff: if any of you have ideas about how to get less fraught behavior out of
BigDecimal I'd like to hear about it on scala/bug#11152
Perhaps we're doing it wrong, but we just ran into an issue building an assembly jar for a project that has spire in its transitive dependencies - it seems that the subprojects of spire each get built with a
buildinfo.BuildInfo$ object, from the sbt-buildinfo plugin. On assembly, these are causing a conflict. I can configure the assembly to discard them but that's a little bit scary. Would it be okay if I made a PR that tried to do one of the following:- put a buildinfo class in a module all to itself that the other modules depend on
- put the buildinfo objects for each subproject in their own packages
sorry, my enumeration failed there
I'd just use a different package
I can take a quick look at it later today and make a PR for it.
maybe there's a way to do that in sbt-buildinfo and fix everything in one go
changing all vals in it to macros would be a start
I think the BuildInfo class is generated at compile time, it should be an object full of
vals
but maybe a better solution than having a class generated at compile time would be inlining the vals from that into the code that uses them
But I agree that it's appealing
all I know
so it basically generates an object with some vals... I think it might be possible to replace them with macros (and eliminate the BuildInfo object from runtime)
actually, why does spire have BuildInfo in the jar?
I used it in https://github.com/kubukoz/sup but only in the microsite
sounds to me like it wouldn't be very useful to the users of the library anyway