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.

Sign up for GitHub

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

Jump to bottom

Order of %use statements should not matter for class loading #354

Closed

holgerbrandl opened this issue Jan 16, 2022 · 0 comments

Labels

bug

Contributor

holgerbrandl commented Jan 16, 2022

Currently, the order in which %use is used to load libraries seems to impact the class-loader's ability to resolve classes.

Example Workbook: https://github.com/holgerbrandl/kravis/blob/6ecb786dbd1b5c138d93d48366ccefd395223055/misc/import_order.ipynb

When flipping the import order it works correctly

Used kernel version: Kotlin kernel v. 0.11.0.45, Kotlin v. 1.6.20-dev-6372

ileasile added the bug label

ileasile closed this as completed in

9dd8240

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment