luke
/
sbt
mirror of https://github.com/sbt/sbt.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify language around SettingKey value "caching"

Havoc Pennington 2011-10-18 15:30:58 -04:00
parent 726d976780
commit fd29e86322
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Getting-Started/Getting-Started-Basic-Def.md

@ -157,7 +157,7 @@ later on.
There are three flavors of key:
- `SettingKey[T]`: a key with a value that never changes (the value is
- `SettingKey[T]`: a key with a value computed once (the value is
computed one time when loading the project, and kept around).
- `TaskKey[T]`: a key with a value that has to be recomputed each time,
potentially creating side effects.

2
Getting-Started/Getting-Started-Custom-Settings.md

@ -38,7 +38,7 @@ building."`).
Remember from [[basic build definition|Getting Started Basic Def]] that the type parameter `T` in `SettingKey[T]`
indicates the type of value a setting has. `T` in `TaskKey[T]` indicates the
type of the task's result. Also remember from [[basic build definition|Getting Started Basic Def]]
that a setting has a fixed value cached forever, while a task is re-computed
that a setting has a fixed value until project reload, while a task is re-computed
for every "task execution" (every time someone types a command at the sbt
interactive prompt or in batch mode).