forked from zclconf/go-cty
-
Notifications
You must be signed in to change notification settings - Fork 3
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: hashicorp/go-cty
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.4.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: hashicorp/go-cty
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.5.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 5 commits
- 13 files changed
- 6 contributors
Commits on Mar 6, 2025
-
Cherry-pick another upstream v1.4.1 change (#9)
* Revert "Forward to v1.4.1 (#7)" This reverts commit 92d5fa8. * convert: fix panic when converting nested objects When converting a list of objects, it is necessary to unify the types of the child elements. * Update CHANGELOG.md * set: Add SameRules method to set.Rules Previously, we checked if two sets had the same rules using a simple equality check. This panics if the sets contain object types, as they cannot be compared using `==`. Adding a SameRules method to the Rules interface allows us to delegate to the Type.Equals method where necessary, fixing this problem. * stdlib: Fix set function crashes with empty sets If one or more arguments to the stdlib set functions was an empty set of dynamic pseudo type, the functions would panic due to incompatible set rules. We can special case empty dynamic pseudo type sets to be ignored through type unification, because they are always capable of being converted to any other type. * Update CHANGELOG.md * v1.4.1 release * Update CHANGELOG.md * Replace import in test --------- Co-authored-by: Kristin Laemmert <mildwonkey@users.noreply.github.com> Co-authored-by: Martin Atkins <mart@degeneration.co.uk> Co-authored-by: Alisdair McDiarmid <alisdair@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 016615a - Browse repository at this point
Copy the full SHA 016615aView commit details -
* Prepare CHANGELOG for a forthcoming 1.4.2 release * function/stdlib: jsonencode should produce a string representation of null * Update CHANGELOG.md * v1.4.2 release * Update CHANGELOG.md --------- Co-authored-by: Martin Atkins <mart@degeneration.co.uk> Co-authored-by: Pam Selle <pamela.selle@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for b56e5cf - Browse repository at this point
Copy the full SHA b56e5cfView commit details -
* Changelog preparation for future 1.4.2 release * convert: Fix panic: heterogeneous tuple with null Tuples with elements of different types can be converted to homogeneous collections (sets or lists), so long as their elements are unifiable. For example: list("a", "b") // all elements have the same type list("a", 5) // "a" and 5 can be unified to string list("a", 5, null) // null is a valid value for string However, tuples with elements which are not unifiable cannot be converted to homogeneous collections: list(["a"], "b") // no common type for list(string) and string This commit fixes a panic for this failure case, when the tuple contains both non-unifiable types and a null value: list(["a"], "b", null) // should not panic The null value was causing the unification process to result in a list or set of dynamic type, which causes the conversion functions to pass through the original value. This meant that in the final conversion step, we would attempt to construct a list or set of different values, which panics. * Update CHANGELOG.md * cty: Value.HasWhollyKnownType This tests whether a value contains any unknown values of unknown type. This is different than just testing if any of the nested types are DynamicPseudoType, because a null value of DynamicPseudoType has a different meaning than an unknown value of DynamicPseudoType: the null value's type can't become any more "known". * Update CHANGELOG.md * v1.5.0 * Update CHANGELOG.md --------- Co-authored-by: Martin Atkins <mart@degeneration.co.uk> Co-authored-by: Alisdair McDiarmid <alisdair@users.noreply.github.com> Co-authored-by: James Bardin <j.bardin@gmail.com>
Configuration menu - View commit details
-
Copy full SHA for 08cd546 - Browse repository at this point
Copy the full SHA 08cd546View commit details
Commits on Mar 17, 2025
-
Update golang.org/x/text (#11)
* Update golang.org/x/text * fixup! Update golang.org/x/text
Configuration menu - View commit details
-
Copy full SHA for f3d5407 - Browse repository at this point
Copy the full SHA f3d5407View commit details -
Configuration menu - View commit details
-
Copy full SHA for f09c453 - Browse repository at this point
Copy the full SHA f09c453View commit details
There are no files selected for viewing