1. 23 Jun, 2021 2 commits
  2. 15 Jun, 2021 1 commit
  3. 14 Jun, 2021 2 commits
  4. 08 Jun, 2021 1 commit
  5. 29 May, 2021 1 commit
  6. 26 May, 2021 1 commit
  7. 12 Apr, 2021 1 commit
  8. 06 Apr, 2021 2 commits
  9. 29 Mar, 2021 1 commit
  10. 26 Feb, 2021 1 commit
  11. 26 Jan, 2021 2 commits
  12. 25 Jan, 2021 3 commits
  13. 22 Jan, 2021 2 commits
  14. 15 Jan, 2021 1 commit
  15. 14 Jan, 2021 1 commit
  16. 12 Jan, 2021 1 commit
  17. 06 Jan, 2021 1 commit
  18. 04 Jan, 2021 1 commit
  19. 12 Nov, 2020 1 commit
  20. 16 Oct, 2020 3 commits
  21. 08 Oct, 2020 1 commit
  22. 06 Oct, 2020 2 commits
  23. 25 Sep, 2020 1 commit
  24. 10 Sep, 2020 1 commit
  25. 07 Jul, 2020 1 commit
  26. 19 Jun, 2020 1 commit
  27. 03 Jun, 2020 2 commits
  28. 30 May, 2020 1 commit
    • Aaron Hill's avatar
      Use proper span when emitting 'self' identifier (#210) · 353db2cf
      Aaron Hill authored
      Normally, the span of a field has the same hygiene context as
      `Span::call_site`. However, it's possible for a struct definition
      to be 'constructed' via a `macro_rules` macro such that the field
      has a different hygiene context. This will cause the expanded code
      to be unable to resolve any references to `self`, resulting in a
      compilation error.
      
      This pull request uses `quote!` instead of `quote_spanned!` when
      emitting a 'self' identifier. `quote_spanned!` is still used for
      everything else in the emitted method, meaning that error messages
      will still point to the proper field.
      
      I've included a test case which triggers this issue on
      Rust 1.43.1. It's current difficult to hit this issue
      other than in this artificial case, but that will change
      once rust-lang/rust#72622 is re-landed.
      353db2cf
  29. 12 May, 2020 1 commit