11
Python Data Model: Copying (programming.dev)
submitted 11 months ago by to c/python@programming.dev
8 comments fedilink hide all child comments
 

An exercise to help build the right mental model for Python data. The “Solution” link uses memory_graph to visualize execution and reveals what’s actually happening:

all 9 comments

sorted by: hot top controversial new old
[–] 6 points 11 months ago (1 child)

id say B

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
    • [–] 1 point 11 months ago (2 children)

    A

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
    • [+] 1 point 10 months ago (1 child)
    [deleted]
  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
    • [–] -3 points 11 months ago (1 child)

    Preferred solution: learnyouahaskell.com . For immutable data!

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
  • [–] [S] 1 point 11 months ago

    Different languages make different choices. The disadvantage of Haskell is that if you want to change one value in a collection of a million values that it either makes a full copy or tries to optimize by sharing values behind the scene, both resulting in significant overhead. Most people already understand that pure functional programming languages don't deliver except in very specific circumstances: Haskell TIOBE rating 0.32%, https://www.tiobe.com/tiobe-index/

  • permalink
  • fedilink
  • source
  • parent