Winapi pseudo calling conv (#277) --- recommendation: accept

Hi all, Proposal 277 is on the topic of a psuedo calling convention for windows, where on x86 you need to use `stdcall`, but on x86_64 it should be `ccall`. The base and Win32 packages both use extensive amounts of CPP to work around this. This proposal is to add a `winapi` calling convention that does the right thing regardless of the platform architecture. With the caveat that I am not well versed in FFI or Windows, *my recommendation is to accept. *This is a very small proposal that can immediately be used to clean up over 650 CPP invocations throughout the ecosystem. It's clearly a problem that people are running into, and we should focus on easy quality of life improvements. As usual, silence will be considered assent! Best, Sandy -- I'm currently travelling the world, sleeping on people's couches and doing full-time collaboration on Haskell projects. If this seems interesting to you, please consider signing up as a host! https://isovector.github.io/erdos/

Link to the proposal:
https://github.com/ghc-proposals/ghc-proposals/pull/277
On Sun, Sep 22, 2019 at 8:44 AM Sandy Maguire
Hi all,
Proposal 277 is on the topic of a psuedo calling convention for windows, where on x86 you need to use `stdcall`, but on x86_64 it should be `ccall`. The base and Win32 packages both use extensive amounts of CPP to work around this.
This proposal is to add a `winapi` calling convention that does the right thing regardless of the platform architecture.
With the caveat that I am not well versed in FFI or Windows, *my recommendation is to accept. *This is a very small proposal that can immediately be used to clean up over 650 CPP invocations throughout the ecosystem. It's clearly a problem that people are running into, and we should focus on easy quality of life improvements.
As usual, silence will be considered assent!
Best, Sandy
-- I'm currently travelling the world, sleeping on people's couches and doing full-time collaboration on Haskell projects. If this seems interesting to you, please consider signing up as a host! https://isovector.github.io/erdos/
-- I'm currently travelling the world, sleeping on people's couches and doing full-time collaboration on Haskell projects. If this seems interesting to you, please consider signing up as a host! https://isovector.github.io/erdos/

Sounds good to me.
Cheers
Simon
On Sun, 22 Sep 2019 at 07:44, Sandy Maguire
Hi all,
Proposal 277 is on the topic of a psuedo calling convention for windows, where on x86 you need to use `stdcall`, but on x86_64 it should be `ccall`. The base and Win32 packages both use extensive amounts of CPP to work around this.
This proposal is to add a `winapi` calling convention that does the right thing regardless of the platform architecture.
With the caveat that I am not well versed in FFI or Windows, *my recommendation is to accept. *This is a very small proposal that can immediately be used to clean up over 650 CPP invocations throughout the ecosystem. It's clearly a problem that people are running into, and we should focus on easy quality of life improvements.
As usual, silence will be considered assent!
Best, Sandy
-- I'm currently travelling the world, sleeping on people's couches and doing full-time collaboration on Haskell projects. If this seems interesting to you, please consider signing up as a host! https://isovector.github.io/erdos/ _______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee

We've now marked this as accepted. Thanks all!
On Mon, Sep 23, 2019 at 9:06 AM Simon Marlow
Sounds good to me.
Cheers Simon
On Sun, 22 Sep 2019 at 07:44, Sandy Maguire
wrote: Hi all,
Proposal 277 is on the topic of a psuedo calling convention for windows, where on x86 you need to use `stdcall`, but on x86_64 it should be `ccall`. The base and Win32 packages both use extensive amounts of CPP to work around this.
This proposal is to add a `winapi` calling convention that does the right thing regardless of the platform architecture.
With the caveat that I am not well versed in FFI or Windows, *my recommendation is to accept. *This is a very small proposal that can immediately be used to clean up over 650 CPP invocations throughout the ecosystem. It's clearly a problem that people are running into, and we should focus on easy quality of life improvements.
As usual, silence will be considered assent!
Best, Sandy
-- I'm currently travelling the world, sleeping on people's couches and doing full-time collaboration on Haskell projects. If this seems interesting to you, please consider signing up as a host! https://isovector.github.io/erdos/ _______________________________________________ ghc-steering-committee mailing list ghc-steering-committee@haskell.org https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee
-- I'm currently travelling the world, sleeping on people's couches and doing full-time collaboration on Haskell projects. If this seems interesting to you, please consider signing up as a host! https://isovector.github.io/erdos/
participants (2)
-
Sandy Maguire
-
Simon Marlow