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: 4821 Reporter:@alainfrisch Status: closed (set by @garrigue on 2009-06-12T12:43:26Z) Resolution: fixed Priority: normal Severity: crash Fixed in version: 3.11.1+dev Category: ~DO NOT USE (was: OCaml general)
Bug description
Consider this piece of code:
class c = object(this)
method m = ignore (this :> < m: unit; m: unit >)
end
let () = (new c) # m
The call to the method yields a segfault (or something similar).
The code generator produces a call to CamlinternalOo.make_class with an array of method being [| "m"; "m" |]. The explicit coercion should probably be rejected (and it is indeed rejected if we use an immediate object rather than a class). Or maybe the type expression (with a duplicated method name) itself should be rejected?
The text was updated successfully, but these errors were encountered:
Original bug ID: 4821
Reporter: @alainfrisch
Status: closed (set by @garrigue on 2009-06-12T12:43:26Z)
Resolution: fixed
Priority: normal
Severity: crash
Fixed in version: 3.11.1+dev
Category: ~DO NOT USE (was: OCaml general)
Bug description
Consider this piece of code:
class c = object(this)
method m = ignore (this :> < m: unit; m: unit >)
end
let () = (new c) # m
The call to the method yields a segfault (or something similar).
The code generator produces a call to CamlinternalOo.make_class with an array of method being [| "m"; "m" |]. The explicit coercion should probably be rejected (and it is indeed rejected if we use an immediate object rather than a class). Or maybe the type expression (with a duplicated method name) itself should be rejected?
The text was updated successfully, but these errors were encountered: