You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 7536 Reporter: Eugene Assigned to:@gasche Status: resolved (set by @gasche on 2017-05-20T15:16:03Z) Resolution: not a bug Priority: normal Severity: feature Version: 4.04.1 Category: standard library
Bug description
Both ocamlc and ocamlopt have -unsafe flag, but sometimes it's more convenient to mix safe and unsafe versions.
Unfortunately, Array module doesn't expose this functions (and Bytes functions, while exposed, isn't documented).
There is one workaround, however (used by Core_kernel, for example) - declare this functions as external. But it is also not very convenient.
The text was updated successfully, but these errors were encountered:
OCaml version 4.05.0+dev8-2017-03-20
# Array.unsafe_get;;
- : 'a array -> int -> 'a =
# Array.unsafe_set;;
- : 'a array -> int -> 'a -> unit =
# Bytes.unsafe_get;;
- : bytes -> int -> char =
# Bytes.unsafe_set;;
- : bytes -> int -> char -> unit =
Original bug ID: 7536
Reporter: Eugene
Assigned to: @gasche
Status: resolved (set by @gasche on 2017-05-20T15:16:03Z)
Resolution: not a bug
Priority: normal
Severity: feature
Version: 4.04.1
Category: standard library
Bug description
Both ocamlc and ocamlopt have -unsafe flag, but sometimes it's more convenient to mix safe and unsafe versions.
Unfortunately, Array module doesn't expose this functions (and Bytes functions, while exposed, isn't documented).
There is one workaround, however (used by Core_kernel, for example) - declare this functions as external. But it is also not very convenient.
The text was updated successfully, but these errors were encountered: