docs(tvix/eval): add notes for builtins access optimisation
Change-Id: Iadbfbe2864ae42fe5492ef3ede0925baee4872b2 Reviewed-on: https://cl.tvl.fyi/c/depot/+/6413 Reviewed-by: sterni <sternenseemann@systemli.org> Tested-by: BuildkiteCI
This commit is contained in:
		
							parent
							
								
									6b3c3c9826
								
							
						
					
					
						commit
						a3b19ad8be
					
				
					 1 changed files with 10 additions and 0 deletions
				
			
		|  | @ -55,3 +55,13 @@ optimisations, but note the most important ones here. | ||||||
|   We can statically detect the conditions for tail-call optimisation. |   We can statically detect the conditions for tail-call optimisation. | ||||||
|   The compiler should do this, and it should then emit a new operation |   The compiler should do this, and it should then emit a new operation | ||||||
|   for doing the tail-calls. |   for doing the tail-calls. | ||||||
|  | 
 | ||||||
|  | * Optimise inner builtin access [medium] | ||||||
|  | 
 | ||||||
|  |   When accessing identifiers like `builtins.foo`, the compiler should | ||||||
|  |   not go through the trouble of setting up the attribute set on the | ||||||
|  |   stack and accessing `foo` from it if it knows that the scope for | ||||||
|  |   `builtins` is unpoisoned. | ||||||
|  | 
 | ||||||
|  |   The same thing goes for resolving `with builtins;`, which should | ||||||
|  |   definitely resolve statically. | ||||||
|  |  | ||||||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue