[3.6 Release] Time to fix the release notes

[Kaelyn Takata]

On Thu, Feb 19, 2015 at 10:05 AM, Hans Wennborg <hans at chromium.org> wrote:

> On Wed, Feb 18, 2015 at 4:34 PM, Hans Wennborg <hans at chromium.org> wrote:
> > The 3.6 release is drawing nearer, but the release notes could still
> > use a lot of improvement:
> >
> > LLVM:
> https://github.com/llvm-mirror/llvm/blob/release_36/docs/ReleaseNotes.rst
> > Clang:
> https://github.com/llvm-mirror/clang/blob/release_36/docs/ReleaseNotes.rst
> >
> > The good news is that they can be updated all the way up until
> > release. If you have a patch for the release notes, commit it directly
> > to the branch, or send it to me and I'll commit it for you. It doesn't
> > even have to be a patch proper, just send me some text!
>
> Kaelyn, do you want to add something about delayed type correction to
> the Clang notes?
>

I'm not sure what would be good to add--while the internal work was pretty
extensive, the only user-visible changes are that the typo suggestions
given are a bit smarter mainly in large or complex translation units
(mostly in more corner-like cases such as getting the right combination of
corrections when a single expression has multiple typos, or where multiple
equally-likely corrections can be disambiguated based on additional
information about the expression in which the typo occurs, or choosing a
textually less-close correction based on e.g. the arguments or return value
if it is a function call). Which is to say, it now tries a bit harder to
give a usable suggestion in more cases, with fewer situations where it
could have suggested something but didn't, or where the suggestion caused
more compilation errors. Oh, and there are now more cases where it can
successfully recover when the suggestion is a keyword that changes how the
expression is parsed.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20150219/9c8bd3d3/attachment.html>