-
Notifications
You must be signed in to change notification settings - Fork 28
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
It seems that, in various cases, it would be nice to have the type-checking at a function call site simply include the semantics of the called function rather than have to write out a specification for it that captures its semantics with enough precision. One use case (sketched here in tests/cn/cn_inline.c) is where a static inline function is used in the computation of a constant. We don't want to have to write out a specification of the function that explains exactly the arithmetic it does, we just want the checking at the call site to reduce the computation down to the constant. The current version is designed to work by annotating the call site with this information rather than annotating the function to be inlined at every call site. This might be revisited. Adjusting the parser to include the new statement required purging and rebuilding the parser error-messages file. Apologies if anyone has manually edited that file, if so, restore from history prior to this point.
- Loading branch information
Showing
9 changed files
with
8,903 additions
and
8,797 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.