Marissa | April

Better support for meaningful SemVer-compliant versions

3

Following on from #93, I think it would be valuable to have the option (even if it is not the default) to produce SemVer-compliant versions. Some thoughts on how to...

Rewrite rule for Map#mapValues should call .view

4

Rewrite rule for `Map#mapValues` should call `.view` before calling `.mapValues` (H/T @joshlemer)

(Micro)Benchmarking reliability and consistency

8

## Motivation A frequent request for scala/scala PRs (particularly collections changes) is that the changes be benchmarked; however, many obstacles exist for contributors running benchmarks on their personal computers, to...

Redesign `NonEmptyLazyList` to be maximally lazy

4

Redesign `NonEmptyLazyList` to be maximally lazy. - [x] docs - [ ] tests - [ ] commit/history cleanup?

Add SeqSet

5

Add `SeqSet`, mirroring `SeqMap`.

Support the creation of Sets from Maps

13

Add implementations for `Set`s backed by `Map`s (and corresponding factories). Add fluent `fromMap` APIs to `Set` companions. Motivation: - It should be first-class - Java has it, why don't we?

add Iterator#dropInPlace

7

`.drop(...)` is equivalent to calling `.next()` (up to) a given number of times, which is very useful. unfortunately, `.drop(...)` is not required to return the same instance (though the default...

Proposals for naming and package structure

25

Proposals: 1. Only names that are planned to exist in a future Scala release can be outside of a `next` (sub-)package. Names that will not exist in a future Scala...

Map builders do not expose methods to add elements without tupling

1

Scala 2.13.x As noted by @smarter [here](https://gitter.im/scala/contributors?at=5f45740736e6f709fd00eec1), builders for `Map`s just use the regular `Builder` interface, and do not expose a way to add elements without creating tuples. However, several...