Jeremy Walker

@tobega I would suggest creating a new exercise that centres around working with unicode characters. This would make a great "Concept Exercise" for Exercism version 3. If you let me...

This feels like it will be very different? In Ruby, for example, Strings are arrays of chars, not bytes, so the test would be a noop (so fine adding it,...

@siebenschlaefer Could you expand a bit more on not adding the test/scenario pair? Doing so would mean that you could opt out for your tracks if you wanted to so...

@siebenschlaefer Thanks for the detailed answer. I understand more what you're saying now. My summary of what I've taken from what you've written is that supporting a few unicode characters...

Because I want some exercises in problem specs to be simple and others to be complex. The nature of all exercises is to become more complex; Exercism's history has consistently...

> it true that some Unicode characters are easier to handle than others and wouldn't warrant having to know the entire Unicode spec That was what I thought before, but...

I don't know the exercise, but as a reference [this is example.py] file in the repo: https://github.com/exercism/python/blob/master/exercises/markdown/example.py#L52-L88 I'm going to move this to the python repo for discussion there.

We'd need someone to lead on this. @emilianbold Is that you? :)

@dag7dev How do you test your code works in RISC-V?

OK, so every exercise on Exercism has tests, which are run to see whether the student's code works or not. This is the code for x86-64-assembly which I guess is...