This build is failing because several of the tests fail due to an "illegal space character." These characters were disallowed in version 0.13.x of the PureScript compiler.

@cdepillabout (or anyone else I should ask?), do you have suggestions on how to handle these tests?

@thomashoneyman Thanks for sending this PR!

Everything looks good here.

This build is failing because several of the tests fail due to an "illegal space character." These characters were disallowed in version 0.13.x of the PureScript compiler.

I took a quick look at the tests, but CI appears to be failing on commit 0aaa87b with the following error (https://github.com/purescript-contrib/purescript-unicode/runs/1212618133#step:8:71):

[1/1 ErrorParsingModule] test/Test/Data/Char/Unicode.purs:78:27

  78          generalCategory '\31' `shouldEqual` Just Control
                                ^
  Unable to parse module:
  Illegal character escape code

It sounds like escaped characters like '\31' are no longer legal? Do you have a suggestion on how to generate ascii character 31 (which, according to man ascii, is hex x1f, US (unit separator))?

Otherwise, I'd be completely fine with just disabling the tests for now and adding an issue about re-enabling them when someone has time to figure out a fix.

Sorry, I misspoke — this is the error I was referring to, and no I unfortunately don’t know how to generate that character for the purpose of the tests. I can disable just the affected three or so tests and open an issue to look into re-enabling them.

I can disable just the affected three or so tests and open an issue to look into re-enabling them.

That sounds like the easiest thing to do for now.

Other than that, I think this looks good.