From: Yawar Amin <yawar.amin@gmail.com>
To: Reed Wilson <cedilla@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Subtyping (or something like it)
Date: Thu, 16 Nov 2017 19:49:50 -0500 [thread overview]
Message-ID: <CAJbYVJLHBPR=RZbWnz1KWmSWQacA5hODsKrvrSZvUX+NOOkWsw@mail.gmail.com> (raw)
In-Reply-To: <CALLFq5QAJixXFyQQVT9sk59dLT3VXfMsEeHiE=U4CxmkNGpbnA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2137 bytes --]
Hi Reed, this is maybe not exactly what you specified, but a `private` type
abbreviation (
https://caml.inria.fr/pub/docs/manual-ocaml/extn.html#s-private-types-abbrev
) should work. You'll have to cast your safe array type to a normal
bigarray to get the indexing and other operations, e.g.:
(my_array : ro t :> (int, int8_unsigned_elt, c_layout) Array1.t).{idx}
Also, see http://camltastic.blogspot.ca/2008/05/phantom-types.html for a
really cool way to mix phantom types and subtyping.
Cheers,
Yawar
On Thu, Nov 16, 2017 at 4:46 PM, Reed Wilson <cedilla@gmail.com> wrote:
> A while ago, I made a module which basically extended bigarrays with a few
> more functions. However, I wanted to have a distinction between read-only
> and read-write values. The equivalence with bigarrays was irrelevant, so my
> interface just looked like this:
>
> type ro
> type rw
> type 'a t
> val read_only : 'a t -> ro t
> val get : 'a t -> int -> int
> val put : rw t -> int -> int -> unit
> ...
>
> Basically, any function that wrote to the type would have to take a "rw
> t", but anything else would take " 'a t". From what I know about C, "ro"
> behaves like the "const" qualifier - not water-proof but it catches some of
> my common mistakes.
>
> Now, however, I want to re-export the equivalence between 'a t and
> bigarrays (mostly for the .{} operator), but also have the
> read-only/read-write distinction. The problem is that if I write:
> type 'a t = (int, int8_unsigned_elt, c_layout) Array1.t
>
> then OCaml will see that "ro t" and "rw t" are the same and freely let me
> use "ro t" values in, for example, the "put" function above.
>
> To summarize, is there a way to make two types internally represented by
> bigarrays, the first of which:
> * can use the bigarray functions (specifically .{} )
> * can use all of my new functions
> and the second type
> * can't use bigarray functions
> * can only use a subset of my new functions
>
> I don't want to have two different versions of each function that I have
> to keep track of.
>
> Thanks,
> Reed Wilson
>
> --
> ç
>
[-- Attachment #2: Type: text/html, Size: 3339 bytes --]
next prev parent reply other threads:[~2017-11-17 0:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 21:46 Reed Wilson
2017-11-17 0:49 ` Yawar Amin [this message]
2017-11-17 2:05 ` Reed Wilson
2017-11-17 13:01 ` octachron
2017-11-17 16:13 ` Reed Wilson
2017-11-17 16:32 ` Leo White
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJbYVJLHBPR=RZbWnz1KWmSWQacA5hODsKrvrSZvUX+NOOkWsw@mail.gmail.com' \
--to=yawar.amin@gmail.com \
--cc=caml-list@inria.fr \
--cc=cedilla@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox