# Regression report stable-2016-08-16 vs. beta-2016-08-26 **URL:** \ **Category:** Uncategorized\ **Created:** [August 27, 2016, 1:35am UTC](https://internals.rust-lang.org/t/regression-report-stable-2016-08-16-vs-beta-2016-08-26/3930 "2016-08-27T01:35:45Z")\ **Posts on this page:** 1\ **Showing post:** 9
**Author:** ![lifthrasiir](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/lifthrasiir/32/24_2.png) [@lifthrasiir](https://internals.rust-lang.org/u/lifthrasiir)\ **Post date:** [August 28, 2016, 5:07pm UTC](https://internals.rust-lang.org/t/regression-report-stable-2016-08-16-vs-beta-2016-08-26/3930/9 "2016-08-28T17:07:23Z")
> [@petrochenkov](#): > > `private_in_public` was reported as a warning since last autumn, i have hard time imagining how a project maintainer can compile his project and look at these warnings for so long and never silence them with `#[allow(private_in_public)]`. As the first crate in the listing (ugh, sorry!), Encoding 0.3 was in the development since early this year (I think) and I had a fix to the warning in the issue list but didn't realize that the 0.2 branch would have the same problem. This is also partly because I haven't set the warning to fail the CI test---but if I had a separate branch for 0.2 I wouldn't be able to see that as new Rust releases do not trigger CI anyway. (So, essentially, same to a pre-1.0 situation.) I've taken this incident as an opportunity to actually apply the fix to 0.3 branch and also published a quick fix as 0.2.33. Still have to think about the long-term maintenance though... --- _[View the full topic](https://internals.rust-lang.org/t/regression-report-stable-2016-08-16-vs-beta-2016-08-26/3930)._