plietar has quit [Read error: Connection reset by peer]
samuell has joined #ponylang
<SeanTAllen>
thanks achambers
lisael1 is now known as lisael
fluttershy_ has joined #ponylang
_andre has joined #ponylang
<fluttershy_>
doublec: hey, is there an easier way to cross compile pony for Android aarch64.
<doublec>
fluttershy_: not that I know of
<fluttershy_>
doublec: does pony support llvm 4 yet ? because then It would be easy to compile ponyc on android.
<doublec>
fluttershy_: why would it be easy?
<fluttershy_>
because termux provide an llvm 4 package already compiled for android
<fluttershy_>
with its package manager
<doublec>
fluttershy_: the main issue is that ponyc hard codes aspects of the platform which is not what you want for cross compilation
<doublec>
fluttershy_: eg. there are checks if building on X86 to do certain things
<fluttershy_>
oh I see.
<doublec>
fluttershy_: nothing that can't be solved though
<fluttershy_>
is anyone working on it ?
<doublec>
fluttershy_: not that I know of
<fluttershy_>
ok ty.
Praetonus has joined #ponylang
plietar_ has quit [Remote host closed the connection]
plietar has joined #ponylang
plietar has quit [Ping timeout: 255 seconds]
fluttershy_ has quit [Quit: Page closed]
<SeanTAllen>
cross compilation is always a pain
<SeanTAllen>
llvm 4 support is underway but not done yet
plietar has joined #ponylang
<SeanTAllen>
you can cross compile pony now but like almost all cross compilation its not fun
Praetonus has quit [Quit: Leaving]
darkav has quit [Ping timeout: 260 seconds]
plietar has quit [Remote host closed the connection]
plietar has joined #ponylang
plietar has quit [Ping timeout: 246 seconds]
plietar has joined #ponylang
amclain has joined #ponylang
pnwamk has quit [Quit: Connection closed for inactivity]
amclain has quit [Ping timeout: 240 seconds]
vaninwagen has quit [Ping timeout: 240 seconds]
obadz has quit [Ping timeout: 240 seconds]
amclain has joined #ponylang
obadz has joined #ponylang
amclain has quit [Ping timeout: 240 seconds]
Matthias247 has joined #ponylang
plietar has quit [Remote host closed the connection]
plietar has joined #ponylang
plietar has quit [Ping timeout: 240 seconds]
fluttershy_ has joined #ponylang
<fluttershy_>
SeanTAllen: yes, it is very difficult. well ty anyway. I'll be waiting for llvm 4 support to test it with termux and see if I get something out of it.
fluttershy_ has quit [Client Quit]
plietar has joined #ponylang
endformationage has joined #ponylang
plietar has quit [Remote host closed the connection]
plietar has joined #ponylang
plietar has quit [Ping timeout: 240 seconds]
plietar has joined #ponylang
emilbayes has quit [Ping timeout: 246 seconds]
plietar has quit [Remote host closed the connection]
emilbayes has joined #ponylang
plietar has joined #ponylang
plietar_ has joined #ponylang
plietar has quit [Read error: Connection reset by peer]
plietar_ has quit [Remote host closed the connection]
plietar has joined #ponylang
plietar has quit [Ping timeout: 240 seconds]
dom96 has quit [Changing host]
dom96 has joined #ponylang
<endformationage>
Hello. I'm wondering how one might use partial application instead of closing over `this_foo` is the following example:
<endformationage>
I couldn't figure out the refcaps to use partial application.
_andre has quit [Quit: leaving]
<endformationage>
I'm also curious as to which might be better to use? I know partial application would create an object literal to wrap the partially applied `finish_up()`, which seemingly could be more expensive than closing over `this_foo` in a hot path?
<SeanTAllen>
what you are doing seems reasonable for as much as i understand the context
<endformationage>
I have an FFI object that has an array of floats, and I wanted to more safely expose a Pony array built from the Pointer[F32], exposing only apply and update operations on the data, so the size can't be mucked with via other Array functions (like push/pop/etc.)
<endformationage>
So I thought I'd expose the data via an object litteral as shown in the example.
<endformationage>
.. with only apply/update funs via the trait
<endformationage>
I wanted to support Pony's `with` syntax for interacting with the data access object, and so also made dispose part of the trait.
<SeanTAllen>
seems reasonable
samuell has quit [Quit: Leaving]
<endformationage>
In my actcual code, finish_up would result in a call to the FFI side of things, further processing the data.