The pragmas have not been as effective as we might have liked, since they only work with templates and can't tell you where in your code you need to make changes, and they seemed to have been more annoying to programmers than helpful, so we're going to discontinue them. We'll leave them in for stuff that's actually been deprecated until deprecated has been improved enough to take a message, but we'll leave "scheduled for deprecation" messages to the documentation and changelog.
It's pretty clear from discussions on the newsgroup that we want to keep toUTF16z, so it shouldn't be scheduled for deprecation anymore. That change is part of D-Programming-Language#279 , but for whatever reason that pull request hasn't been reviewed yet, let alone merged in, and this change shouldn't need review, _and_ it should be in before the next release, so I'm just making it and checking it in. It's simply removing the "scheduled for deprecation" note in the documentation and its associated pragma.
I've also greatly improved the comments for pow.
…m access ranges are required to have a length now anyhow, use a more efficient method of filling the index range that doesn't require iterating over the range to be sorted.