Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "function coloring" to glossary #155

Merged
merged 2 commits into from
Oct 10, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions terminology.md
Original file line number Diff line number Diff line change
Expand Up @@ -510,6 +510,21 @@ While this is not an explicitly adopted goal of TC39, it is a common standards c

[HTML Design Principles](https://www.w3.org/TR/html-design-principles/#priority-of-constituencies)

## Function coloring

### Definition
bakkot marked this conversation as resolved.
Show resolved Hide resolved
The observation that it is annoying to have two kinds of functions, with one kind of function easily usable from the other but not conversely.

Originally referred to async and sync functions (it is hard to use an async function from a sync function), though it applies to other possible attributes of functions as well.

### Example

Having `unsafe` functions which are only callable from other `unsafe` functions, while other functions are callable anywhere, would create a new kind of function coloring.

### References

[What Color is Your Function?](https://journal.stuffwithstuff.com/2015/02/01/what-color-is-your-function/)

## Contributing to This Document

Here are some tips and ideas for adding a [new definition](#definition-template) to this document.
Expand Down
Loading