Bug 18187 – std.uni.Grapheme should be usable in @safe

Status
RESOLVED
Resolution
FIXED
Severity
enhancement
Priority
P1
Component
phobos
Product
D
Version
D2
Platform
x86_64
OS
All
Creation time
2018-01-03T04:54:29Z
Last change time
2021-10-19T13:18:15Z
Assigned to
No Owner
Creator
Seb
Blocks
18110

Comments

Comment #0 by greensunny12 — 2018-01-03T04:54:29Z
see e.g. std.uni.decodeGrapheme or std.uni.byGrapheme
Comment #1 by john.loughran.colvin — 2018-03-22T18:57:53Z
Do you have an example? Changing the unittests for those 2 functions to be @safe just works for me.
Comment #2 by greensunny12 — 2018-03-22T19:03:33Z
That's great then. There have been a few changed in std.uni recently, e.g. https://github.com/dlang/phobos/pull/6041 So maybe these changes made the test @safe There's also the fact that Phobos's testsuite now uses -dip1000 to test std.uni, but I just checked and it seems like the tests are now @safe even without -dip1000 :) Up for a quick PR?
Comment #3 by john.loughran.colvin — 2018-03-22T21:31:36Z