1. 22 8月, 2018 3 次提交
  2. 20 8月, 2018 3 次提交
  3. 19 8月, 2018 1 次提交
  4. 10 8月, 2018 2 次提交
  5. 09 8月, 2018 1 次提交
  6. 27 7月, 2018 1 次提交
  7. 25 7月, 2018 1 次提交
  8. 24 7月, 2018 1 次提交
  9. 20 7月, 2018 1 次提交
  10. 18 7月, 2018 3 次提交
  11. 16 7月, 2018 1 次提交
  12. 14 7月, 2018 1 次提交
  13. 08 7月, 2018 1 次提交
  14. 02 7月, 2018 2 次提交
  15. 01 7月, 2018 1 次提交
    • Z
      in which hir::Visibility recalls whence it came (i.e., becomes Spanned) · 4ae89129
      Zack M. Davis 提交于
      There are at least a couple (and plausibly even three) diagnostics that
      could use the spans of visibility modifiers in order to be reliably
      correct (rather than hacking and munging surrounding spans to try to
      infer where the visibility keyword must have been).
      
      We follow the naming convention established by the other `Spanned` HIR
      nodes: the "outer" type alias gets the "prime" node-type name, the
      "inner" enum gets the name suffixed with an underscore, and the variant
      names are prefixed with the prime name and `pub use` exported from here
      (from HIR).
      
      Thanks to veteran reviewer Vadim Petrochenkov for suggesting this
      uniform approach. (A previous draft, based on the reasoning that
      `Visibility::Inherited` should not have a span, tried to hack in a named
      `span` field on `Visibility::Restricted` and a positional field on
      `Public` and `Crate`. This was ... not so uniform.)
      4ae89129
  16. 28 6月, 2018 3 次提交
  17. 26 6月, 2018 1 次提交
  18. 24 6月, 2018 1 次提交
  19. 20 6月, 2018 4 次提交
  20. 19 6月, 2018 1 次提交
  21. 15 6月, 2018 1 次提交
  22. 14 6月, 2018 2 次提交
  23. 06 6月, 2018 1 次提交
  24. 01 6月, 2018 2 次提交
  25. 29 5月, 2018 1 次提交