Mirror of forum.nim-lang.org

4050 :: META-discussion on concepts and memory views

• Bulat_Ziganshin (orginal) [2018-07-15T18:51:09+02:00] view original

  Issue tracker contains a lot of issues discussing two closely related things - container concepts and idea of MemoryView objects. I propose to do the following:

  • start/assign exactly two issues for general discussion of each topic and in particular comparing proposals over each other
  • use separate issue for discussion of each particular proposal, i.e. one issue per one proposal
  • list these issues in the headers of corresponding general issues
  • mark all but general issues/PRs as closed, and create new proposals as closed from the start

  Ideally, each topic should have coordinator and header message of the topic should be editable by him.

  Issues dealing with container concepts:

  • https://github.com/nim-lang/Nim/issues/7337
  • https://github.com/nim-lang/Nim/issues/7041
  • https://github.com/nim-lang/Nim/issues/5753
  • https://github.com/nim-lang/Nim/issues/6528

  Issues/code dealing with memory views:

  • https://github.com/nim-lang/Nim/issues/5437
  • https://github.com/nim-lang/Nim/pull/5957
  • https://github.com/nim-lang/Nim/issues/7337
  • https://github.com/nim-lang/Nim/issues/8256
  • https://github.com/status-im/nim-ranges/blob/master/ranges/typedranges.nim

---

• mratsim (orginal) [2018-07-16T11:40:20+02:00] view original

  Currently:

  • Concepts are managed by @zah
  • Openarray design is managed by @Araq and openarrays will be extended to cover memory views/spans/ranges/slices and pointer + len pairs (which they already are implementation-wise).

---

• Araq (orginal) [2018-07-16T18:41:59+02:00] view original

  Well, we need both. openarray as a kind of (borrowed pointer, length) pair, and an Indexable concept to base algorithms on. I don't think these two should be conflated. The guarantee for a contiguous memory block is very useful to have in a systems programming language.

---