about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
diff options
context:
space:
mode:
authorJacob Pratt <jacob@jhpratt.dev>2025-07-07 03:26:09 +0200
committerGitHub <noreply@github.com>2025-07-07 03:26:09 +0200
commitc6be76206fc05d9425208343888203bbc214f6d3 (patch)
treedb141fabfdd0a0a5f10c2dbd4fceeeb8eb294e3c /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
parent8aad0e6ad9c0a31f458c62529ccbe1708c12b560 (diff)
parent491c8feaabff3c941a30d02c0c2a2622acf257e3 (diff)
downloadrust-c6be76206fc05d9425208343888203bbc214f6d3.tar.gz
rust-c6be76206fc05d9425208343888203bbc214f6d3.zip
Rollup merge of #143544 - workingjubilee:rename-bare-fn, r=fmease
compiler: rename BareFn to FnPtr

At some point "BareFn" was the chosen name for a "bare" function, without the niceties of `~fn`, `&fn`, or a few other ways of writing a function type. However, at some point the syntax for a "bare function" and any other function diverged even more. We started calling them what they are: function pointers, denoted by their own syntax.

However, we never changed the *internal* name for these, as this divergence was very gradual. Personally, I have repeatedly searched for "FnPtr" and gotten confused until I find the name is BareFn, only to forget this until the next time, since I don't routinely interact with the higher-level AST and HIR. But even tools that interact with these internal types only touch on them in a few places, making a migration easy enough. Let's use a more intuitive and obvious name, as this 12+ year old name has little to do with current Rust.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions