Most of the time, we don't need to have a dynamic call sub graph, since the actual function call could be represented statically as it originally was before lambda functions were implemented. Simplifying the graph shape has important performance benefits in terms of both keep the graph smaller (memory, etc) and in avoiding the need to run transactions at runtime (speed) to reshape the graph. Co-authored-by: Samuel Gélineau <gelisam@gmail.com>
30 lines
734 B
Plaintext
30 lines
734 B
Plaintext
-- main.mcl --
|
|
import "fmt"
|
|
|
|
# these two resources are identical to each other, so we should allow it
|
|
file "/tmp/foo" {
|
|
content => "hello world",
|
|
}
|
|
file "/tmp/foo" {
|
|
content => fmt.printf("hello world"),
|
|
}
|
|
|
|
# these two resources are compatible with each other, so we should allow it
|
|
pkg "cowsay" {
|
|
state => "installed",
|
|
}
|
|
pkg "cowsay" {
|
|
state => "newest",
|
|
}
|
|
-- OUTPUT --
|
|
Edge: const: str("hello world") -> printf: func(format str) str # format
|
|
Vertex: const: str("/tmp/foo")
|
|
Vertex: const: str("/tmp/foo")
|
|
Vertex: const: str("cowsay")
|
|
Vertex: const: str("cowsay")
|
|
Vertex: const: str("hello world")
|
|
Vertex: const: str("hello world")
|
|
Vertex: const: str("installed")
|
|
Vertex: const: str("newest")
|
|
Vertex: printf: func(format str) str
|