At the moment I'm sending feedback to students with numbering like the following:
```markdown3. I'm not sure this is an issue with literals, as our VM doesn't support pointers or dereferencing in any obvious way. But I grant you the point.
4. This answer says both that `loadfun` would have to change and that "the loader shouldn't have to change. These statements aren't internally consistent (only one can be true). As for functions returning, no change is needed to `VMFunction`. All that's needed is a `Return` instruction.
5. Nice thinking about cache effects.
<!--comment-->
7. Good thinking. Later on we'll see that it is sufficient to be sure that every execution path in a function ends with a `Return` instruction.
8. I didn't make the Booleans static because I wanted a `mkBooleanValue` with a dynamic argument. Adding static values has no payoff. (A `Value` fits in two hardware registers.)
<!--comment-->
10. Nice work.
```
If I ever forget to include `<!--comment-->`, the feedback goes to the student with the wrong number.
I know that the Markdown specification says that items in ordered lists will be renumbered. But is there a way to tell pandoc not to do that?
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/9c5112a4-b699-4f82-b962-c4f5e8cd55can%40googlegroups.com.