- 
                Notifications
    You must be signed in to change notification settings 
- Fork 231
Implement DateFromFieldsError, a narrow error type for Date::try_from_fields #7100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
          
     Merged
      
      
    
  
     Merged
                    Changes from 8 commits
      Commits
    
    
            Show all changes
          
          
            15 commits
          
        
        Select commit
          Hold shift + click to select a range
      
      7e6a1f6
              
                Initial migration to DateFromFieldsError
              
              
                sffc 219caa9
              
                Fix up docs tests
              
              
                sffc 1c904dd
              
                ci
              
              
                sffc 37267ab
              
                passing tests
              
              
                sffc 9af0e42
              
                Error mapping commentary
              
              
                sffc ab70a67
              
                try_parse
              
              
                sffc 753bbdf
              
                clippy, fmt
              
              
                sffc c4b2e3c
              
                use enums for all errors
              
              
                sffc 50b78f7
              
                Remove MonthCode field from DateFromFieldsError
              
              
                sffc 1de767e
              
                Merge branch 'main' into datefromfieldserror
              
              
                sffc ffc284c
              
                diplomat-coverage
              
              
                sffc e78a06d
              
                Fix errors in FFI and in new coverage test
              
              
                sffc b5b027f
              
                Fix rust link
              
              
                sffc 0624665
              
                Add re-exports to diplomat-coverage allowlist
              
              
                sffc f2de676
              
                diplomat-gen
              
              
                sffc File filter
Filter by extension
Conversations
          Failed to load comments.   
        
        
          
      Loading
        
  Jump to
        
          Jump to file
        
      
      
          Failed to load files.   
        
        
          
      Loading
        
  Diff view
Diff view
There are no files selected for viewing
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
              
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
              
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
              
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
              
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
              
      
      Oops, something went wrong.
        
    
  
      
      Oops, something went wrong.
        
    
  
  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.
  
    
  
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion: if we allow invalid month codes to be constructed, this method should take
ordinal: u8, is_leap: boolto remove the parsing error case (or introduce a newValidMonthCodetype). once we move to&strinputs we basically don't needMonthCodeanymore.this also applies to all other (internal) methods that use
MonthCode. validate early so not every method needs aInvalidMonthCodeerror variantThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i cautiously like this idea, though I think it can be a non-2.1 blocking followup as a part of graduating these traits.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it can only be non-blocking if we don't sprinkle
MonthCodein other parts of the API, like error variants, and the input itselfThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, sure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you both are okay with adding
icu_calendar::types::ValidMonthCode, I will proceed with that.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm in favor of that. This issue is a mandatory 2.1 blocker so we can do things piecemeal
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Looked at the PR, not in favor of the PR, stated why there)
I think here we can have MonthCode, or a tuple, or an unstable lightweight
ValidMonthCodetype. The latter two are more optimized, and we can change our mind when graduating the trait. We should note this thing as a decision-to-be-made on the graduation issue and move on.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a decision about unstable code and does not block this PR, nor should its fix involve public stable API changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can make ValidMonthCode pub(crate)/unstable in the other PR for now, and remove it from the error variant. I think in both cases where we convert to DateError, we have access to the input month code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, that works!