anchor.diff:  ///
   /// This semantic index is not necessarily the same as the index of the widget in
   /// the scrollable, because some widgets may not contribute semantic
  -/// information. Consider a [new ListView.separated()]: every other widget is a
  +/// information. Consider a [ListView.separated]: every other widget is a
   /// divider with no semantic information. In this case, only odd numbered
   /// widgets have a semantic index (equal to the index ~/ 2). Furthermore, the
   /// total number of children in this example would be half the number of
  -/// widgets. (The [new ListView.separated()] constructor handles this
  +/// widgets. (The [ListView.separated] constructor handles this
   /// automatically; this is only used here as an example.)
   ///
   /// The total number of visible children can be provided by the constructor
  
positive.code: ///
  /// The [childrenDelegate] property on [ListView] corresponds to the
  /// [SliverList.delegate] (or [SliverFixedExtentList.delegate]) property. The
  /// [new ListView] constructor's `children` argument corresponds to the
  /// [childrenDelegate] being a [SliverChildListDelegate] with that same
  /// argument. The [new ListView.builder] constructor's `itemBuilder` and
  /// `itemCount` arguments correspond to the [childrenDelegate] being a
  /// [SliverChildBuilderDelegate] with the equivalent arguments.
  ///
  
negative.code:   /// The `itemBuilder` should actually create the widget instances when called.
    /// Avoid using a builder that returns a previously-constructed widget; if the
    /// list view's children are created in advance, or all at once when the
    /// [ListView] itself is created, it is more efficient to use the [ListView]
    /// constructor. Even more efficient, however, is to create the instances on
    /// demand using this constructor's `itemBuilder` callback.
    ///
    /// The `addAutomaticKeepAlives` argument corresponds to the
    /// [SliverChildBuilderDelegate.addAutomaticKeepAlives] property. The
  