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

[0.8] Warn on non definite number of fields instead of failing #209

Merged
merged 1 commit into from
Feb 2, 2022

Conversation

vchuravy
Copy link
Member

@vchuravy vchuravy commented Feb 2, 2022

No description provided.

@codecov-commenter
Copy link

codecov-commenter commented Feb 2, 2022

Codecov Report

Merging #209 (47cb618) into release-0.8 (0186c5d) will decrease coverage by 0.05%.
The diff coverage is 50.00%.

Impacted file tree graph

@@               Coverage Diff               @@
##           release-0.8     #209      +/-   ##
===============================================
- Coverage        79.71%   79.66%   -0.06%     
===============================================
  Files               12       12              
  Lines             2366     2370       +4     
===============================================
+ Hits              1886     1888       +2     
- Misses             480      482       +2     
Impacted Files Coverage Δ
src/typetree.jl 85.00% <50.00%> (-1.46%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0186c5d...47cb618. Read the comment docs.

@vchuravy vchuravy changed the title Warn on non definite number of fields instead of failing [0.8] Warn on non definite number of fields instead of failing Feb 2, 2022
tt(T) = string(typetree(T, ctx, dl))

@testset "TypeTree" begin
@test tt(Float16) == "{[0]:Float@half}" # TODO(VC) inconsistent
Copy link
Member Author

Choose a reason for hiding this comment

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

@wsmoses this should probably be [-1] as well?

Copy link
Member

Choose a reason for hiding this comment

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

It should be, yes

@vchuravy vchuravy merged commit b6cc619 into release-0.8 Feb 2, 2022
@vchuravy vchuravy deleted the vc/fc branch February 2, 2022 14:23
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