Update readme.md, package info and release notes

Author: abelbraaksma

README.md

@@ -319,8 +319,8 @@ This is what has been implemented so far, is planned or skipped:
 | ✅ [#90][] | `singleton`        | `singleton`          |                           | |
 | ✅ [#209][]| `skip`             | `skip`               |                           | |
 | ✅ [#209][]|                    | `drop`               |                           | |
-|                  | `skipWhile`        | `skipWhile`          | `skipWhileAsync`          | |
-|                  |                    | `skipWhileInclusive` | `skipWhileInclusiveAsync` | |
+| ✅ [#219][]| `skipWhile`        | `skipWhile`          | `skipWhileAsync`          | |
+| ✅ [#219][]|                    | `skipWhileInclusive` | `skipWhileInclusiveAsync` | |
 | ❓         | `sort`             |                      |                           | [note #1](#note1 "These functions require a form of pre-materializing through 'TaskSeq.cache', similar to the approach taken in the corresponding 'Seq' functions. It doesn't make much sense to have a cached async sequence. However, 'AsyncSeq' does implement these, so we'll probably do so eventually as well.") |
 | ❓         | `sortBy`           |                      |                           | [note #1](#note1 "These functions require a form of pre-materializing through 'TaskSeq.cache', similar to the approach taken in the corresponding 'Seq' functions. It doesn't make much sense to have a cached async sequence. However, 'AsyncSeq' does implement these, so we'll probably do so eventually as well.") |
 | ❓         | `sortByAscending`  |                      |                           | [note #1](#note1 "These functions require a form of pre-materializing through 'TaskSeq.cache', similar to the approach taken in the corresponding 'Seq' functions. It doesn't make much sense to have a cached async sequence. However, 'AsyncSeq' does implement these, so we'll probably do so eventually as well.") |
@@ -603,6 +603,7 @@ module TaskSeq =
 [#133]: https://github.com/fsprojects/FSharp.Control.TaskSeq/issues/133
 [#209]: https://github.com/fsprojects/FSharp.Control.TaskSeq/issues/209
 [#217]: https://github.com/fsprojects/FSharp.Control.TaskSeq/issues/217
+[#219]: https://github.com/fsprojects/FSharp.Control.TaskSeq/issues/219
 
 [issues]: https://github.com/fsprojects/FSharp.Control.TaskSeq/issues
 [nuget]: https://www.nuget.org/packages/FSharp.Control.TaskSeq/

assets/nuget-package-readme.md

@@ -199,8 +199,8 @@ This is what has been implemented so far, is planned or skipped:
 | ✅ [#90][] | `singleton`        | `singleton`          |                           | |
 | ✅ [#209][]| `skip`             | `skip`               |                           | |
 | ✅ [#209][]|                    | `drop`               |                           | |
-|                  | `skipWhile`        | `skipWhile`          | `skipWhileAsync`          | |
-|                  |                    | `skipWhileInclusive` | `skipWhileInclusiveAsync` | |
+| ✅ [#219][]| `skipWhile`        | `skipWhile`          | `skipWhileAsync`          | |
+| ✅ [#219][]|                    | `skipWhileInclusive` | `skipWhileInclusiveAsync` | |
 | ❓         | `sort`             |                      |                           | [note #1](#note1 "These functions require a form of pre-materializing through 'TaskSeq.cache', similar to the approach taken in the corresponding 'Seq' functions. It doesn't make much sense to have a cached async sequence. However, 'AsyncSeq' does implement these, so we'll probably do so eventually as well.") |
 | ❓         | `sortBy`           |                      |                           | [note #1](#note1 "These functions require a form of pre-materializing through 'TaskSeq.cache', similar to the approach taken in the corresponding 'Seq' functions. It doesn't make much sense to have a cached async sequence. However, 'AsyncSeq' does implement these, so we'll probably do so eventually as well.") |
 | ❓         | `sortByAscending`  |                      |                           | [note #1](#note1 "These functions require a form of pre-materializing through 'TaskSeq.cache', similar to the approach taken in the corresponding 'Seq' functions. It doesn't make much sense to have a cached async sequence. However, 'AsyncSeq' does implement these, so we'll probably do so eventually as well.") |
@@ -308,3 +308,4 @@ _The motivation for `readOnly` in `Seq` is that a cast from a mutable array or l
 [#126]: https://github.com/fsprojects/FSharp.Control.TaskSeq/pull/126
 [#209]: https://github.com/fsprojects/FSharp.Control.TaskSeq/issues/209
 [#217]: https://github.com/fsprojects/FSharp.Control.TaskSeq/issues/217
+[#219]: https://github.com/fsprojects/FSharp.Control.TaskSeq/issues/219

release-notes.txt

@@ -3,9 +3,10 @@ Release notes:
 0.4.x (unreleased)
     - overhaul all doc comments, add exceptions, improve IDE quick-info experience, #136
     - new surface area functions, fixes #208:
-      * TaskSeq.take, TaskSeq.skip, #209
-      * TaskSeq.truncate, TaskSeq.drop, #209
-      * TaskSeq.where, TaskSeq.whereAsync, #217
+      * TaskSeq.take, skip, #209
+      * TaskSeq.truncate, drop, #209
+      * TaskSeq.where, whereAsync, #217
+      * TaskSeq.skipWhile, skipWhileInclusive, skipWhileAsync, skipWhileInclusiveAsync, #219
 
     - Performance: less thread hops with 'StartImmediateAsTask' instead of 'StartAsTask', fixes #135
     - BINARY INCOMPATIBILITY: 'TaskSeq' module is now static members on 'TaskSeq<_>', fixes #184