aiken/crates
KtorZ d3885ac67a
prune orphan pair definitions after full blueprint generation.
This is to avoid pruning a definition which may end up needed later
  on. The issue can be seen when definition to a Pair is used *before*
  another Map definitions that uses this same Pair.

  Before this commit, the Map definition would simply remove the
  definition generated for the Pair, since it would be pointless (and it
  is a lot easier to generate those pointless definition than trying to
  remember we are currently generating definition for a Map).

  So now, we defer the removal of the orphan definition to after all
  defnitions have been generated by basically looking at a dependency
  graph. I _could have_ used pet-graph on this to solve it similar to
  how we do package dependencies; but given that we only really need to
  that for pairs, the problem is relatively simple to solve (though
  cumbersome since we need to traverse all defintions).

  Fixes #1086.
2025-01-30 15:51:43 +01:00
..
aiken Addressed comments on benchmarking PR 2025-01-22 15:23:17 -08:00
aiken-lang Fix: additional tipo case when using Pairs type inside of a redeemer or datum type 2025-01-30 18:54:14 +07:00
aiken-lsp Trigger warning when destructuring records using unnamed fields 2025-01-22 18:07:57 -05:00
aiken-project prune orphan pair definitions after full blueprint generation. 2025-01-30 15:51:43 +01:00
uplc chore: Release 2025-01-21 23:48:15 +07:00