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

Jump to bottom

Macro for defining type of schedule #145

Closed
Anders429 opened this issue Nov 23, 2022 · 0 comments
Closed

Macro for defining type of schedule #145

Anders429 opened this issue Nov 23, 2022 · 0 comments
Labels
A - Scheduling Area: Parallel scheduling of systems. C - Enhancement Category: New feature or request. F - rayon Feature: Parallel processing through the rayon library. P - Low Priority: Not particularly urgent. V - Minor Breaking Change Versioning: Requires a minor bump according to semver.

Comments

@Anders429
Copy link
Owner

In many cases, it is helpful to store the type of a schedule. Since schedules are created with macros to hide the nesting, the same can be done for the type of a schedule.

Consider introducing a Schedule! macro to do this. Note the capitalization, which is in line with #141.
@Anders429 Anders429 added C - Enhancement Category: New feature or request. P - Low Priority: Not particularly urgent. F - rayon Feature: Parallel processing through the rayon library. A - Scheduling Area: Parallel scheduling of systems. V - Minor Breaking Change Versioning: Requires a minor bump according to semver. labels Nov 23, 2022
@Anders429 Anders429 mentioned this issue Nov 25, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A - Scheduling Area: Parallel scheduling of systems. C - Enhancement Category: New feature or request. F - rayon Feature: Parallel processing through the rayon library. P - Low Priority: Not particularly urgent. V - Minor Breaking Change Versioning: Requires a minor bump according to semver.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Anders429