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

Handle polyalgorithm aliasing correctly #392

Merged
merged 1 commit into from
Mar 21, 2024

Conversation

avik-pal
Copy link
Member

Aliasing is messy 😓

Copy link

codecov bot commented Mar 21, 2024

Codecov Report

Attention: Patch coverage is 73.84615% with 17 lines in your changes are missing coverage. Please review.

Project coverage is 86.73%. Comparing base (e1c0528) to head (45e0716).

Files Patch % Lines
src/default.jl 72.88% 16 Missing ⚠️
src/utils.jl 83.33% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #392      +/-   ##
==========================================
- Coverage   86.92%   86.73%   -0.19%     
==========================================
  Files          46       46              
  Lines        2760     2797      +37     
==========================================
+ Hits         2399     2426      +27     
- Misses        361      371      +10     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@avik-pal avik-pal self-assigned this Mar 21, 2024
@ChrisRackauckas
Copy link
Member

Yes, I want a whole aliasing system in general, but this'll do for now.

@ChrisRackauckas ChrisRackauckas merged commit 3925219 into master Mar 21, 2024
12 of 17 checks passed
@ChrisRackauckas ChrisRackauckas deleted the ap/reliable_aliasing branch March 21, 2024 22:40
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.

2 participants