0 views collected around this technical thread.
This article explains step by step how Python creates a function object, builds a call stack, handles parameters, executes the body, performs garbage collection, and manages recursion, illustrating each stage with clear code examples and diagrams.
The article explains that Go maps and slices are not safe for concurrent reads or writes, describes how the runtime detects map violations, and recommends using sync.Mutex, sync.RWMutex, or sync.Map for maps and external synchronization for slices, while also clarifying that passing these reference types to functions shares underlying data unless explicitly copied.
This article explains the difference between value passing and reference passing in Java, clarifies how primitive and object types are stored in stack and heap, and demonstrates the behavior with concrete code examples showing how modifications affect (or do not affect) the original arguments.
This article explains why swapping Integer objects using a simple assignment fails in Java, covering formal vs. actual parameters, value versus reference passing, autoboxing mechanics, the Integer cache, and a reflective workaround that avoids the cache to correctly exchange values.
This article clarifies the long‑standing confusion about whether Java uses pass‑by‑value or pass‑by‑reference by defining the concepts, distinguishing actual and formal parameters, and demonstrating with primitive and object examples that Java always passes arguments by value, using the reference as the value for objects.
This article explains the distinction between value passing and reference passing in Java by examining the JVM memory layout, the roles of the stack, heap, and method area, and demonstrates how primitive and object parameters behave through detailed code examples and visual diagrams.
This article explains Python's id() function, how objects and references work, and demonstrates parameter passing behavior with detailed code examples illustrating memory address handling for immutable and mutable types, including lists, integers, and strings, and clarifies why variable assignments may share the same address.
This article explains how Java's `new` keyword allocates objects on the heap, how object references reside on the stack, the relationship between references and objects, the mechanics of reference assignment, garbage collection conditions, and why Java uses value‑passing for method parameters.