=item *
-They have some tricks Perl doesn't yet implement like character
-class subtraction.
+UTF-8 identifier names should probably be canonicalized: NFC?
- http://www.unicode.org/unicode/reports/tr18/
+=item *
+
+UTF-8 in package names and sub names? The first is problematic
+because of the mapping to pathnames, ditto for the second one if
+one does autosplitting, for example.
=back
See L<perlunicode/UNICODE REGULAR EXPRESSION SUPPORT LEVEL> for what's
there and what's missing. Almost all of Levels 2 and 3 is missing,
and as of 5.8.0 not even all of Level 1 is there.
+They have some tricks Perl doesn't yet implement, such as character
+class subtraction.
+
+ http://www.unicode.org/unicode/reports/tr18/
=head2 use Thread for iThreads
This should be allowed if the new keyset is a subset of the old
keyset. May require more extra code than we'd like in pp_aassign.
+=head2 Should overload be inheritable?
+
+Should overload be 'contagious' through @ISA so that derived classes
+would inherit their base classes' overload definitions? What to do
+in case of overload conflicts?
+
+=head2 Taint rethink
+
+Should taint be stopped from affecting control flow, if ($tainted)?
+Should tainted symbolic method calls and subref calls be stopped?
+(Look at Ruby's $SAFE levels for inspiration?)
+
=head1 Vague ideas
Ideas which have been discussed, and which may or may not happen.
requires some thought. Remember that an OS does not implicate a
filesystem.
+Note that in Windows the -C command line flag already does quite
+a bit of the above (but even there the support is not complete:
+for example the exec/spawn are not Unicode-aware) by turning on
+the so-called "wide API support".
+
=head1 Recently done things
These are things which have been on the todo lists in previous releases