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

Feature/fix box contains #953

Merged
merged 2 commits into from
Aug 21, 2019
Merged

Feature/fix box contains #953

merged 2 commits into from
Aug 21, 2019

Conversation

jvbsl
Copy link
Contributor

@jvbsl jvbsl commented Aug 20, 2019

  • Use latest C# version(necessary for me with dotnet 3.0 preview, doesn't seem to recognize 7.3)
  • Make contains boundary exclusive, as tests do test for that -> fixed tests by doing that
  • Make contains overload with bool parameter to test boundary inclusive as well
  • Use boundary inclusive contains for inflate tests

* box contains check is non boundary inclusive by default now
* Fixed box contains tests
* Add boundary inclusive box contains check
* Use boundary inclusive box contains check for inflate test

[<Property>]
let ``Box2.Inflate is equivelant to Box2.Inflated`` (b1 : Box3, v1 : Vector3) =
let ``Box2.Inflate is equivalent to Box2.Inflated`` (b1 : Box3, v1 : Vector3) =
Copy link
Contributor

Choose a reason for hiding this comment

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

lol that change, hilarious. Good catch! 🥇

Copy link
Member

@varon varon left a comment

Choose a reason for hiding this comment

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

Perfect fix!

@varon
Copy link
Member

varon commented Aug 21, 2019

We've got a little code duplication here; the overload should probably defer to the other method.

I'll merge for now as this fixes our tests!

@varon varon merged commit 751b273 into opentk:master Aug 21, 2019
@varon
Copy link
Member

varon commented Aug 21, 2019

Thanks a ton @jvbsl !

@jvbsl
Copy link
Contributor Author

jvbsl commented Aug 21, 2019

the code duplication was on purpose for now, for performance, and I didn't want to AggressiveInline everything :D

@varon
Copy link
Member

varon commented Aug 21, 2019

Figures. Hence the merge.

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