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: 5492 Reporter:@lefessan Status: closed (set by @diml on 2016-12-07T17:27:35Z) Resolution: open Priority: normal Severity: feature Version: 3.13.0+dev Category: -for Camlp4 use https://github.com/ocaml/camlp4/issues Tags: patch Monitored by:@xclerc
Bug description
Since any new construct in the language should be tested in the testsuite/, we should always verify that camlp4o generates correct code for these new constructs, to be sure that a new release is not shipped with no support for some new construct in camlp4o.
The patch looks very incomplete to me, as it applies only to tests of the "several" kind.
It might be worthwhile to have a way to run the testsuite using camlp4o, but I wouldn't want this to be done at every run of the testsuite. One reason is that we need to be able to test new features before camlp4 is updated to support them. Another reason is that several of us developers configure with -no-camlp4 to speed up compiles during development.
Original bug ID: 5492
Reporter: @lefessan
Status: closed (set by @diml on 2016-12-07T17:27:35Z)
Resolution: open
Priority: normal
Severity: feature
Version: 3.13.0+dev
Category: -for Camlp4 use https://github.com/ocaml/camlp4/issues
Tags: patch
Monitored by: @xclerc
Bug description
Since any new construct in the language should be tested in the testsuite/, we should always verify that camlp4o generates correct code for these new constructs, to be sure that a new release is not shipped with no support for some new construct in camlp4o.
A patch to the testsuite/ makefile is provided.
File attachments
The text was updated successfully, but these errors were encountered: