feijoas / mango Goto Github PK

trait RangeSetLike in org.feijoas.mango.common.collect.immutable has the same methods as in mutable version.
But in guava ImmutableRangeSet has "difference" method I need, which is missing in mango
https://google.github.io/guava/releases/21.0/api/docs/com/google/common/collect/ImmutableRangeSet.html#difference-com.google.common.collect.RangeSet-
I cannot do a workaraound because Guava Range and RangeSet are private in mango and thus not exposed

Why does e.g. Range take a type parameter O <: Ordering[T] instead of just having the implicit val ord: Ordering[T] like in a scala collection. The current way forces me to always specify the ordering when using Range types.

This looks great, thanks!

I'm getting the following 'unresolved dependency' error using the instructions verbatim from the README:

[info] Resolving org.feijoas#mango_2.11;0.11 ...
[warn]  module not found: org.feijoas#mango_2.11;0.11
[warn] ==== local: tried
[warn]   /Users/test/.ivy2/local/org.feijoas/mango_2.11/0.11/ivys/ivy.xml
[warn] ==== public: tried
[warn]   https://repo1.maven.org/maven2/org/feijoas/mango_2.11/0.11/mango_2.11-0.11.pom
[warn] ==== typesafe repo: tried
[warn]   http://repo.typesafe.com/typesafe/releases/org/feijoas/mango_2.11/0.11/mango_2.11-0.11.pom
[warn] ==== spray repo: tried
[warn]   http://repo.spray.io/org/feijoas/mango_2.11/0.11/mango_2.11-0.11.pom
[warn] ==== Sonatype Snapshots: tried
[warn]   http://oss.sonatype.org/content/repositories/snapshots/org/feijoas/mango_2.11/0.11/mango_2.11-0.11.pom
[warn] ==== Sonatype Releases: tried
[warn]   https://oss.sonatype.org/content/repositories/releases/org/feijoas/mango_2.11/0.11/mango_2.11-0.11.pom
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  ::          UNRESOLVED DEPENDENCIES         ::
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  :: org.feijoas#mango_2.11;0.11: not found
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::

While put and remove are supported for the mutable RangeMap implementation, the immutable version does not have these methods (neither does the guava interface). When looking at the immutable scala collections, they all support modifying methods which just return a new collection. Wouldn't it make sense to implement something similar for the immutable Guava collections?

If you attempt to build a project that depends on Mango with Maven you will get something similar to:
2/24/15, 3:44:28 PM PST: [ERROR] Could not resolve artifact com.google.code.findbugs:jsr305:pom:1.3.+

See sbt/sbt#1136 for background.

Maybe republishing with the latest sbt would resolve the issue?

I'm using mango with 2.10 now mostly just for cache and it's been awesome! Are you still maintaining this and keeping up to date? It'd be great if a 2.11 jar was provided as well.

For my own use, could I just change the target version in SBT and rebuild?

Mango currently uses Guava 14.0.1.

We are updating an app to use scala 2.12 and I do not see a mango_2.12 build artifact in maven. Is there any effort to get a 2.12 build artifact out there? Thanks

From what I can see, LoadingCache.getAll doesn't seem to actually invoke CacheLoader.loadAll, as it states in the docs. Unless I'm missing some clever indirection.