Skip to content

Conversation

@carsonRadtke
Copy link
Contributor

@carsonRadtke carsonRadtke commented Mar 3, 2025

@hsutter
Copy link
Contributor

hsutter commented Apr 15, 2025

Editors call: Thanks, looks good but please:

  • @GabrielDosReis add a note that by design there are no iterator/pointer-invalidating operations (other than the destructor)
  • ensure that there is no assignment (neither copy nor move)
  • add wording for move construction

- Make sure iterators and references cannot be invalidated by any
  operations (besides destruction).
- Update specification to annotate that some functions require certain
  language features (ranges and concepts).
- Remove dependence on "Container" named requirements because they
  require iterator-invalidating behavior.
- Explicitly add default and move constructors.
- Fix some typos
Clarified that `gsl::dyn_array` cannot be moved or copied. Updated the FAQ section to emphasize that it is a fixed-size array without iterator/pointer-invalidating operations.
@GabrielDosReis
Copy link
Contributor

Editors call: Thanks, looks good but please:

* @GabrielDosReis add a note that by design there are no iterator/pointer-invalidating operations (other than the destructor)

* ensure that there is no assignment (neither copy nor move)

* add wording for move construction

Done.

Clarified the purpose of gsl::dyn_array in the FAQ section.
@hsutter
Copy link
Contributor

hsutter commented Dec 3, 2025

Editors call: Looks great, thank you!

@hsutter hsutter merged commit 4e1e155 into isocpp:master Dec 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Provide a specifcation for gsl::dyn_array

3 participants