Skip to content

Revise compiler options for binding graph fixes #5110

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

Open
TWiStErRob wants to merge 1 commit into
base: gh-pages
Choose a base branch
from
Open

Revise compiler options for binding graph fixes #5110

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions dev-guide/compiler-options.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,13 +10,13 @@ redirect_from:
In v2.55, Dagger introduced a rewrite of its core binding graph creation logic
that fixes many subtle bugs that have plague the previous version. However,
these fixes also come with a behavior change (see details below), so we've
introduced a flag to ease the migration to the new behavior. To enable the
fixes, pass the following compiler option:
introduced a flag to ease the migration to the new behavior. This was enabled
by default in v2.58. To disable the fixes, pass the following compiler option:

`-Adagger.useBindingGraphFix=ENABLED`.
`-Adagger.useBindingGraphFix=disabled`

In a future release, we will enable this flag by default, and remove the flag
entirely once users have had a chance to migrate.
In a future release, we will remove this flag entirely once users have had a
chance to migrate.

### Background

Expand Down