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

til::point #4897

Merged
2 commits merged into from
Mar 13, 2020
Merged

til::point #4897

2 commits merged into from
Mar 13, 2020

Conversation

miniksa
Copy link
Member

@miniksa miniksa commented Mar 12, 2020

Summary of the Pull Request

Introduces convenience type til::point which automatically implements our best practices for point-related types and provides automatic conversions in/out of the relevant types.

PR Checklist

Detailed Description of the Pull Request / Additional comments

  • Automatically converts in from anything with a X/Y (console COORD) or x/y (Win32 POINT)
  • Automatically converts out to COORD, POINT, or D2D1_POINT_2F.
  • Constructs from bare integers written into source file
  • Default constructs to empty
  • Uses Chromium Math for all basic math operations (+, -, *, /)
  • Provides equality tests
  • Accessors for x/y
  • Type converting accessors (that use safe conversions and throw) for x/y
  • TAEF/WEX Output and Comparators so they will print very nicely with VERIFY and Log macros in our testing suite.
  • A natvis

Validation Steps Performed

  • See automated tests of functionality.

@miniksa miniksa added Product-Meta The product is the management of the products. Issue-Task It's a feature request, but it doesn't really need a major design. Area-CodeHealth Issues related to code cleanliness, linting, rules, warnings, errors, static analysis, etc. labels Mar 12, 2020
@miniksa miniksa self-assigned this Mar 12, 2020
@miniksa
Copy link
Member Author

miniksa commented Mar 12, 2020

NOTE: This is going to look an awful lot like til::size (#4850) and that's on purpose. I want them to be completely separate types so they don't combine into each other in any way like COORD has historically done in our codebase in reference to both sizes and points. I also want to give them the opportunity to evolve separately if need be, say, if something like "area" makes sense for a size but not for a point.

@miniksa miniksa added the AutoMerge Marked for automatic merge by the bot when requirements are met label Mar 13, 2020
@ghost
Copy link

ghost commented Mar 13, 2020

Hello @miniksa!

Because this pull request has the AutoMerge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

Do note that I've been instructed to only help merge pull requests of this repository that have been opened for at least 8 hours, a condition that will be fulfilled in about 4 hours 22 minutes. No worries though, I will be back when the time is right! 😉

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@miniksa
Copy link
Member Author

miniksa commented Mar 13, 2020

@msftbot merge in 1 minute

@ghost
Copy link

ghost commented Mar 13, 2020

Hello @miniksa!

Because you've given me some instructions on how to help merge this pull request, I'll be modifying my merge approach. Here's how I understand your requirements for merging this pull request:

  • I won't merge this pull request until after the UTC date Fri, 13 Mar 2020 00:04:14 GMT, which is in 1 minute

If this doesn't seem right to you, you can tell me to cancel these instructions and use the auto-merge policy that has been configured for this repository. Try telling me "forget everything I just told you".

@ghost ghost merged commit 068e3e7 into master Mar 13, 2020
@ghost ghost deleted the dev/miniksa/til_point branch March 13, 2020 00:04
@miniksa miniksa mentioned this pull request Mar 13, 2020
4 tasks
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-CodeHealth Issues related to code cleanliness, linting, rules, warnings, errors, static analysis, etc. AutoMerge Marked for automatic merge by the bot when requirements are met Issue-Task It's a feature request, but it doesn't really need a major design. Product-Meta The product is the management of the products.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants