| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Return SpawnResults using a List instead of a Set. |  ruperts | 2017-11-21 |
| | | | | | | | | | | Currently we don't care about the list order of SpawnResults. However, we may care about the list order later. Also, if the equals() method for SpawnResults is ever changed then it may be problematic to return SpawnResults in a Set. Aside: ActionResults use SpawnResults to calculate cumulative execution times for Actions, and may provide other metrics in future. RELNOTES: None. PiperOrigin-RevId: 176579460 | ||
| * | More SpawnResult-related plumbing changes to Actions, Strategies, ↵ | ruperts | 2017-10-07 |
| ActionContexts, etc., so that SpawnResult metadata is returned upwards. Note that the TODOs mostly refer to changes that will appear in a subsequent CL (a CL to return SpawnResults, contained in ActionResults, from Actions/AbstractActions). I split off the remaining SpawnResult-related changes into this CL and kept the ActionResult-related changes separate. RELNOTES: None. PiperOrigin-RevId: 171355611 | |||
 |
index : bazel | |
| a fast, scalable, multi-language and extensible build system |
| aboutsummaryrefslogtreecommitdiffhomepage |