Skip to content
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

update the match flags to 64 bit #294

Merged
merged 10 commits into from
May 23, 2023
Merged

update the match flags to 64 bit #294

merged 10 commits into from
May 23, 2023

Conversation

phlptp
Copy link
Collaborator

@phlptp phlptp commented May 16, 2023

adjust some things with the partitioning, add a minimum partitioning size and better handling of degrees.

Inspired by #293

phlptp and others added 2 commits May 16, 2023 08:05
…itioning, add a minimum partitioning size and better handling of degrees
Comment on lines +21 to +23
// EXPECT_EQ(ucum | astronomy, allDomains);
// EXPECT_EQ(ucum | nuclear, allDomains);
// EXPECT_EQ(nuclear | astronomy, allDomains);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Intentionally commented?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am changing the domain codes so this relationship doesn't hold at present, there may be further modifications to restore them but not sure what the best approach is yet.

Comment on lines +999 to +1002
u1 = unit_from_string("gramm");
EXPECT_EQ(u1, precise::g * precise::m);
u1 = unit_from_string("kilogramm");
EXPECT_EQ(u1, precise::kilo * precise::g * precise::m);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel that this is a very surprising behavior. Mixing full words (kilo and gram) with symbols (m), especially without an operator or spacing in between is not really intuitive and of limited use? Supporting gram*m and gram m seems ok, but gramm?

Comment on lines 1004 to 1005
// u1 = unit_from_string("inchy");
// EXPECT_EQ(u1,precise::kilo*precise::g*precise::m);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Commented code?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there for testing to see what "inchy" actually did, will be removed before merging

@codecov-commenter
Copy link

codecov-commenter commented May 17, 2023

Codecov Report

Merging #294 (ab08313) into main (7065585) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #294   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            9         9           
  Lines         4626      4655   +29     
=========================================
+ Hits          4626      4655   +29     

@phlptp phlptp changed the title update the match flags to 64 bit and update the match flags to 64 bit May 18, 2023
@phlptp phlptp merged commit 879c5b0 into main May 23, 2023
43 checks passed
@phlptp phlptp deleted the match_flags_update branch May 23, 2023 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants