mers/examples/get_ref.mers

list = [1 2 3 4 5 6 7 8 9 ...]

// calling get on an &list will get a reference
&list.get(2).assume1() = 24
// calling get on a list will get a value
should_not_be_changeable = list.get(3).assume1()
&should_not_be_changeable = 24

if list.get(2) != [24] println("[!!] list.get(2) != 24 (was {0})".format(list.get(2).to_string()))
if list.get(3) == [24] println("[!!] list.get(3) == 24")

list.debug()
completely changed the VData/VDataEnum system: Multiple VData can share one VDataEnum via an Arc<Mutex<VDataEnum>>. If one wants to modify the data, it copies it (Copy on Write). This copying is skipped for shared mutable data (references). This was necessary for the get_ref() function. Expect bugs! 2023-05-11 01:04:15 +02:00			`list = [1 2 3 4 5 6 7 8 9 ...]`

fixed examples 2023-05-23 23:56:45 +02:00			`// calling get on an &list will get a reference`
			`&list.get(2).assume1() = 24`
			`// calling get on a list will get a value`
			`should_not_be_changeable = list.get(3).assume1()`
			`&should_not_be_changeable = 24`
changed VData system again, renamed src/script to src/lang and added src/c.mers, which is an example something that currently does not work properly due to the VData implementation (and serves as a reminder to fix the issue) 2023-05-14 00:11:36 +02:00
			`if list.get(2) != [24] println("[!!] list.get(2) != 24 (was {0})".format(list.get(2).to_string()))`
			`if list.get(3) == [24] println("[!!] list.get(3) == 24")`
completely changed the VData/VDataEnum system: Multiple VData can share one VDataEnum via an Arc<Mutex<VDataEnum>>. If one wants to modify the data, it copies it (Copy on Write). This copying is skipped for shared mutable data (references). This was necessary for the get_ref() function. Expect bugs! 2023-05-11 01:04:15 +02:00
			`list.debug()`