memory-tests.eo:32-38: Let's make sure memory can only...

[0pdd]

The puzzle 761-525f7f4a from #761 has to be resolved:

eo/eo-runtime/src/test/eo/org/eolang/memory-tests.eo

Lines 32 to 38 in f9df2ae

	# @todo #761:30min Let's make sure memory can only accept one "type" of data primitives.
	# If we try to write a float into a memory that was initialized with an int, we should
	# get an error. The same goes for strings and booleans. We should also make sure that
	# we can't write a string that is longer than the memory size. We should also make sure
	# that we can't write a number that is bigger than the memory size. And etc.
	# We can also implement memory in EO instead of Java and let it use ram object.
	# Let's not forget to update the "Origins of Objects" paper.

The puzzle was created by @rultor on 05-Jul-23.

Estimate: 30 minutes, role: DEV.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

[Graur]

@yegor256 Should tuple saving in memory be prohibit?

[yegor256]

@Graur yes, only int, float, string, and bool are allowed

[Graur]

@yegor256 Should a memory object only work with bytes? For example:

memory "hello" > mem
QQ.io.stdout mem.as-string # will print "hello"
QQ.io.stdout mem # will print some bytes

[yegor256]

@Graur I didn't get the question. The code you suggested should work. What's wrong with it?

[Graur]

@yegor256 I would like to suggest a new implementation for the return value when storing a primitive object in memory. When we write memory "hello" > mem, the mem object should contain bytes instead of a string. In the current implementation of the memory object, it returns the string object "hello".

[yegor256]

@Graur in this case this code won't work:

memory 42 > x
x.write (x.plus 1)

Here, x.plus will fail with no method .plus in bytes. Right?

[Graur]

@yegor256 Yes, you are right

[0pdd]

@0pdd 2 puzzles #2434, #2435 are still not solved.

[0pdd]

@0pdd 2 puzzles #2434, #2452 are still not solved; solved: #2435.

[0pdd]

@0pdd the puzzle #2434 is still not solved; solved: #2435, #2452.