Syntax lenses are very single-purpose

[jackfirth]

I initially made these for use in very specific problems in other projects. They don't really belong in the general lens package, at least not with the same status as the other lenses. Possible fixes include:

• Move to a lens/unstable collection or something that similarly signals they're not to be relied upon heavily. This would prevent them from getting locked into the API forever with 1.0
• Move to an entirely separate package which provides a lens/syntax collection. There would probably have to be more syntax lenses to justify this, but it would give the most flexibility as that package could be versioned and managed separately.
• Remove them from the package catalog entirely and just keep them as private to wherever I needed them originally.

They should probably be excluded from 1.0 and hidden until it's decided what to do with them.

[jackfirth]

#86 removed syntax lenses, making this no longer necessary for 1.0

[AlexKnauth]

A lens/syntax/... sub-collection makes sense to me.

[jackfirth]

That definitely makes sense as a final destination, but it should probably initially be provided in something which doesn't commit to backwards compatibility as I'm pretty unsure what else should go in such a collection or whether these lenses should be named differently or have different semantics. Perhaps an unstable/lens/syntax collection to start with?