#ChronoGrapher - One Unified Scheduler, Unlimited Power

1 messages · Page 7 of 1

fervent lark
#

if only there was a way to make know concrete types easily

#

oh ye

#

the issues are getting real

#

singletons....

#

like come the fuck on

#

why does Rust have to ruin this

#

i really don't want everything erased

#

first was schedule, now its the TaskFrame

fervent lark
#

turns out its solveable

#

it requires an associated type inside the TaskFrame

fervent lark
#

finally

#

with just two tradeoffs

#

i've managed to make the task and workflow work

#

the first is you are not allowed to use any kind of expression in TaskFrames

#

for 99% of cases this is basically a non-issue

#

you have two choices, using the type directly allows you to reference its entire workflow, if you don't want that then use @ followed by the type

#

to only get the raw code

#

the second is the introduction of a new associated type in the TaskFrame called Workflow

#

in every case, you should always make it equal to Self

#

its a helper for the macro, when it generates your TaskFrame, it writes to it the entire type

fervent lark
#

the workflow proc-macro API docs will be massive, arguably the biggest by far

fervent lark
#

im left with depedency and condition