Stream: git-wasmtime

Topic: wasmtime / Issue #1703 Split `peepmatic_runtime::linear::...

Wasmtime GitHub notifications bot (May 14 2020 at 16:33):

fitzgen opened Issue #1703:

Right now we have an Increment that represents both the linearized LHS and linearized RHS of an optimization. This is a historical accident from an earlier design where they were interleaved with each other. Now that they are not, and only the first increment has any RHS Actions, we should just split Increment into two types: one for LHSes and one for RHSes. The linear::Optimization would have a member of each type, instead of just a vec of increments.

Wasmtime GitHub notifications bot (May 14 2020 at 16:33):

fitzgen labeled Issue #1703:

Right now we have an Increment that represents both the linearized LHS and linearized RHS of an optimization. This is a historical accident from an earlier design where they were interleaved with each other. Now that they are not, and only the first increment has any RHS Actions, we should just split Increment into two types: one for LHSes and one for RHSes. The linear::Optimization would have a member of each type, instead of just a vec of increments.

Last updated: Dec 23 2024 at 12:05 UTC