diff options
| author | Lars Kanis <lars@greiz-reinsdorf.de> | 2023-04-26 14:50:29 +0200 |
|---|---|---|
| committer | Lars Kanis <lars@greiz-reinsdorf.de> | 2023-04-27 13:47:57 +0200 |
| commit | 0093113f07d1878d6f70480cdc1bf95c09fb7c2a (patch) | |
| tree | 1cd14ee99ab73756de95792d41d2697f2609d033 /spec/ffi/variadic_spec.rb | |
| parent | 4fc6a8c5ec8a9a720330946af9d1103015c62942 (diff) | |
| download | ffi-0093113f07d1878d6f70480cdc1bf95c09fb7c2a.tar.gz | |
Rename result_type to return_type
The term "return_type" is already used in Truffleruby and sounds better to me.
On the other hand the term "result_type" was only used in C-ffi as FunctionInfo#result_type, which is an internal class only.
Diffstat (limited to 'spec/ffi/variadic_spec.rb')
| -rw-r--r-- | spec/ffi/variadic_spec.rb | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/spec/ffi/variadic_spec.rb b/spec/ffi/variadic_spec.rb index 283878b..917212a 100644 --- a/spec/ffi/variadic_spec.rb +++ b/spec/ffi/variadic_spec.rb @@ -40,7 +40,7 @@ describe "Function with variadic arguments" do it "can reveal its return and parameters" do fun = LibTest.attached_functions["testBlockingWRva"] expect(fun.param_types).to eq([FFI::Type::POINTER, FFI::Type::CHAR, FFI::Type::VARARGS]) - expect(fun.result_type).to eq(FFI::Type::INT8) + expect(fun.return_type).to eq(FFI::Type::INT8) end it 'can wrap a blocking function with varargs' do |