Consider moving reader macro tests to their respective steps about mal HOT 2 CLOSED

So, I realized this morning why this won't work. Step 1 is unique from the following steps because it doesn't yet have eval. So it's the only place you can test reader/printer functionality directly.

# In step 1
user> `7
(quote 7)
# steps 2 - 6 give an error
# step 7
user> `7
7

So, while it's not ideal, I think having these tests in step1 and marked as optional/deferrable is probably the best option without adding significant complication in the test runner or in the steps (e.g. a command line option to disable evaluation, ugh).

Closing.

from mal.

Alright, that makes sense.

from mal.