Skip to content

Conversation

@c42f
Copy link
Member

@c42f c42f commented Apr 3, 2020

These are only duplicated for better stack traces, and are otherwise meant to be the same. However the code here has already started to diverge in several minor but confusing ways (#34595 etc) which is making a larger refactor related to #35243 more fiddly.

Factor the include bodies into a macro to improve this.

This also allows the bulk of the code to go in loading.jl which I find a little more natural.

These are only duplicated for better stack traces, and are otherwise
meant to be the same. However the code here has already started to
diverge in several minor but confusing ways. Factor the bodies into a
macro to fix this.
@c42f c42f requested a review from vtjnash April 3, 2020 02:45
@vtjnash
Copy link
Member

vtjnash commented Apr 3, 2020

I thought this should have the same backtraces as if it were actually just a function? But we appear to already have added mapexpr concept there now too, so that seems like it already ruined the concept there.

@c42f
Copy link
Member Author

c42f commented Apr 3, 2020

Ah that's embarrassing. I forgot macros have a special handling for backtraces 🤦‍♂️

Hold on, I've got another idea.

@c42f
Copy link
Member Author

c42f commented Apr 6, 2020

Replaced by #35371

@c42f c42f closed this Apr 6, 2020
@DilumAluthge DilumAluthge deleted the cjf/cleanup-base-include branch March 25, 2021 22:04
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.

3 participants