1. 16 11月, 2018 1 次提交
  2. 03 11月, 2018 1 次提交
  3. 13 10月, 2018 1 次提交
  4. 09 10月, 2018 1 次提交
  5. 03 10月, 2018 1 次提交
  6. 11 9月, 2018 2 次提交
  7. 10 9月, 2018 1 次提交
  8. 06 9月, 2018 1 次提交
  9. 22 8月, 2018 3 次提交
  10. 17 5月, 2018 1 次提交
  11. 11 5月, 2018 1 次提交
  12. 08 5月, 2018 1 次提交
  13. 27 4月, 2018 1 次提交
  14. 14 3月, 2018 1 次提交
    • A
      remove defaulting to unit · 9b15ddb2
      Andrew Cann 提交于
      Types will no longer default to `()`, instead always defaulting to `!`.
      This disables the associated warning and removes the flag from TyTuple
      9b15ddb2
  15. 13 3月, 2018 1 次提交
    • N
      transition various normalization functions to the new methods · e4728e49
      Niko Matsakis 提交于
      In particular:
      
      - `fully_normalize_monormophic_ty` => `normalize_erasing_regions`
      - `normalize_associated_type_in_env` => `normalize_erasing_regions`
      - `fully_normalize_associated_types_in` => `normalize_erasing_regions`
      - `erase_late_bound_regions_and_normalize` => `normalize_erasing_late_bound_regions`
      e4728e49
  16. 08 3月, 2018 1 次提交
  17. 23 1月, 2018 1 次提交
  18. 14 1月, 2018 2 次提交
  19. 06 12月, 2017 1 次提交
  20. 28 10月, 2017 1 次提交
  21. 11 9月, 2017 1 次提交
  22. 05 9月, 2017 1 次提交
    • A
      rustc: Store InternedString in `DefPathData` · 0cdc58a1
      Alex Crichton 提交于
      Previously a `Symbol` was stored there, but this ended up causing hash
      collisions in situations that otherwise shouldn't have a hash collision. Only
      the symbol's string value was hashed, but it was possible for distinct symbols
      to have the same string value, fooling various calcuations into thinking that
      these paths *didn't* need disambiguating data when in fact they did!
      
      By storing `InternedString` instead we're hopefully triggering all the exising
      logic to disambiguate paths with same-name `Symbol` but actually distinct
      locations.
      0cdc58a1
  23. 12 8月, 2017 1 次提交
  24. 28 7月, 2017 1 次提交
  25. 20 7月, 2017 1 次提交
  26. 14 7月, 2017 1 次提交
  27. 27 6月, 2017 1 次提交
  28. 25 2月, 2017 1 次提交
  29. 03 2月, 2017 1 次提交
  30. 31 1月, 2017 1 次提交
  31. 06 12月, 2016 2 次提交
  32. 29 11月, 2016 1 次提交
  33. 28 11月, 2016 1 次提交
  34. 21 11月, 2016 1 次提交
  35. 14 10月, 2016 1 次提交
    • A
      normalize types every time HR regions are erased · ee338c31
      Ariel Ben-Yehuda 提交于
      Associated type normalization is inhibited by higher-ranked regions.
      Therefore, every time we erase them, we must re-normalize.
      
      I was meaning to introduce this change some time ago, but we used
      to erase regions in generic context, which broke this terribly (because
      you can't always normalize in a generic context). That seems to be gone
      now.
      
      Ensure this by having a `erase_late_bound_regions_and_normalize`
      function.
      
      Fixes #37109 (the missing call was in mir::block).
      ee338c31