Remove Either documentation page
#4400
Conversation
docs/faq.md
Outdated
| This syntax and the type class instances for `Either` can be imported using `cats.syntax._`, which will also bring in syntactic enrichment and instances for other standard library types, or you can import only the `Either` enrichment with `cats.syntax.either._`. | ||
|
|
||
| There are a few minor mismatches between `Xor` and `Either`. For example, in some cases you may need to specify a type parameter for an enrichment method on `Either` (such as `leftMap`) even though it was properly inferred for `Xor`. See the [`Either` section of this guide](datatypes/either.md#either-in-the-small-either-in-the-large) for more information about these issues. | ||
| There are a few minor mismatches between `Xor` and `Either`. For example, in some cases you may need to specify a type parameter for an enrichment method on `Either` (such as `leftMap`) even though it was properly inferred for `Xor`, due `Either` having covariant type parameters. |
There was a problem hiding this comment.
I updated this, but is this still an FAQ two major versions later?
armanbilge
changed the title
Either documentation page.
reardonj
force-pushed
the
remove-obsolete-either-documentation
branch
from
cbd8e65
to
a2408ba
Compare
|
Sorry, one final thought: instead of completely 404ing the page can we put something there to redirect inbound links somewhere more useful? |
I perused the Laika documentation, but I don't see a way to have a page exist without it showing up in the table of contents. Is there something in the Typelevel site setup to allow such a redirect? |
Jens on Discord:
Not sure if that's supported in Laika 0.18.x, if not I might need to get the sbt-typelevel upgrade PR in first. |
danicheg
changed the title
Either documentation page.Either documentation page
Resolves #4392
StateTdocumentation in the right order