You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@arrow.apache.org by "Neal Richardson (Jira)" <ji...@apache.org> on 2021/02/05 16:00:00 UTC

[jira] [Updated] (ARROW-11351) [JavaScript] Reconsider proxy objects instead of defineProperty

     [ https://issues.apache.org/jira/browse/ARROW-11351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Neal Richardson updated ARROW-11351:
------------------------------------
    Summary: [JavaScript] Reconsider proxy objects instead of defineProperty  (was: Reconsider proxy objects instead of defineProperty)

> [JavaScript] Reconsider proxy objects instead of defineProperty
> ---------------------------------------------------------------
>
>                 Key: ARROW-11351
>                 URL: https://issues.apache.org/jira/browse/ARROW-11351
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: JavaScript
>            Reporter: Dominik Moritz
>            Priority: Major
>
> I was wondering why Arrow uses Proxy objects instead of defineProperty, which was a bit faster in the experiments at https://observablehq.com/@jheer/from-apache-arrow-to-javascript-objects. I don't know whether a change makes sense but I would love to know the design rationale since I couldn't find anything in the issues or on GitHub about it. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)