Overhaul tuple macro to use a drop guard #9
                
     Merged
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Current tuple macro will correctly drop initialized fields when an error is encountered. But, it does not use a drop guard like the derive macros currently do, so it's not panic safe.
Generating correct drop guard logic with
macro_rulesgets exceptionally ugly, and thus hard to understand and maintain. This PR rewrites the current tuple macro into a function that generates aTokenStream(like a proc-macro) so that the implementation is much easier to reason about (doesn't require multiple recursing declarative macros), in addition to using drop guard like the derive macros so that we're panic safe.I've also bundled this into a build step so that we don't require a separate crate to expose a proc-macro, which would have to be independently versioned and published.