Splat parameters are currently moved into a tuple. def foo(*x) x end typeof(foo(1, true)) # => Tuple(Int32, Bool) It would be nice if splatting could support other collection types, including dynamically sized ones. This is not useful for forwarding parameters, one of the primary purposes of sp…

I extracted the thread about #values_at into Splatting in `#values_at` because it’s not directly related to array splatting. The key point for this discussion: Splat parameters should be able to receive splat arguments (and forward them): def foo(*x : *Array(Bool | Int32)) x end tuple = {1, tr…

But this is to be restricted to a limited number of builtin types? Or how would the compiler know how to create and populate instances of user defined collection types?

For example, the compiler would rewrite these arguments: foo(1, true) to create an array-like literal and pass that instead. foo(Array(Bool | Int32){1, true}) Which then further expands to something like this: %temp = Array(Bool | Int32).new %temp << 1 %temp << true foo(%temp) So custom types …

[Idea] Splat def parameters into array

Topic		Replies	Views
Easiest way to convert an array of strings to a splattable tuple? Help & Support	3	374	September 8, 2023
How to fix the Ruby code which a splatting array as parameter Help & Support	8	323	November 4, 2022
Is there any plan for support double splatting a NamedTuple union? Crystal Contrib	22	640	July 10, 2024
Converting an array to its elements Help & Support	3	495	June 8, 2021
Method with splat arguments, which captures a block which takes the same number of arguments Help & Support	2	232	February 9, 2024

[Idea] Splat def parameters into array

Related topics