deprecation warnings running single-file example

[ilmanzo]

../../../../.dub/packages/scriptlike-0.10.2/scriptlike/src/scriptlike/path/extras.d(25,8): Deprecation: module `std.path` member osDefaultCaseSensitivity is not visible from module extras
../../../../.dub/packages/scriptlike-0.10.2/scriptlike/src/scriptlike/path/wrappers.d(26,15): Deprecation: module `std.path` member osDefaultCaseSensitivity is not visible from module wrappers
../../../../.dub/packages/scriptlike-0.10.2/scriptlike/src/scriptlike/interact.d(173,24): Deprecation: function `std.string.removechars!string.removechars` is deprecated - This function is obsolete and will be removed May 2018. See the docs for more details
../../../../.dub/packages/scriptlike-0.10.2/scriptlike/src/scriptlike/path/extras.d(25,8): Deprecation: module `std.path` member osDefaultCaseSensitivity is not visible from module extras
../../../../.dub/packages/scriptlike-0.10.2/scriptlike/src/scriptlike/path/wrappers.d(26,15): Deprecation: module `std.path` member osDefaultCaseSensitivity is not visible from module wrappers

[ilmanzo]

tests$ ./testExample SingleFile
Testing SingleFile
    Testing from its own directory...
core.exception.AssertError@./testExample.d(300): Assertion failure
----------------
??:? _d_assertp [0xfee2899d]
??:? void testExample.testUseInScripts(immutable(char)[], scriptlike.path.extras.Path, immutable(char)[], bool) [0xfee1e60c]
??:? void testExample.testSingleFile() [0xfee1eb74]
??:? _Dmain [0xfee1d4f3]

[Abscissa]

The deprecation messages should be fixed in master as of 91d6d46d1b3dbeb8e12e7996bc4924bd165ccba1 (the removechars message fixed in the previous commit, 77bac758008335daea1a8f8b2d0c2f88820109ff). The test failure is most likely just because the test runner isn't expecting the deprecation messages to show up in the output. (That's been a common problem. I should probably change the test runner to separate build vs run).

I haven't issued a new release yet mainly because I'm still trying to get Windows CI testing up and running through AppVeyor, and there's still some issues remaining with that.