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.

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

chore: add debug symbols to release build & some comments #439

Merged
merged 1 commit into from
Oct 20, 2023
Merged

chore: add debug symbols to release build & some comments #439

Show file tree
Hide file tree
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
3 changes: 3 additions & 0 deletions Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,3 +65,6 @@ required-features = ["ff"]
[profile.dev]
opt-level = 0
debug = true

[profile.release]
debug = 1 # For profiling, should be disabled for production builds
4 changes: 4 additions & 0 deletions examples/jssp/problem/individual.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -289,6 +289,10 @@ impl JsspIndividual {
let op_j = &self.operations[j];

// Calculate the earliest finish time (in terms of precedence only)
// TODO: We do not need to look on all predecessors. The direct one is enough, as
// it could not be scheduled before all his preds were finished. The question is:
// is the order of predecessors guaranteed? Look for places that manipulate this
// field!
let pred_j_finish = op_j
.preds
.iter()
Expand Down