Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
GHC
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Terraform modules
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Gesh
GHC
Commits
62cb9a07
Commit
62cb9a07
authored
25 years ago
by
Reuben Thomas
Browse files
Options
Downloads
Patches
Plain Diff
[project @ 2000-01-26 16:08:25 by rrt]
Corrected release notes URLs
parent
4c892ba0
Loading
Loading
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
ghc/ANNOUNCE
+2
-2
2 additions, 2 deletions
ghc/ANNOUNCE
with
2 additions
and
2 deletions
ghc/ANNOUNCE
+
2
−
2
View file @
62cb9a07
...
...
@@ -44,14 +44,14 @@ Apart from that, there are the following changes
except (alas) on stdout/stderr for tiresome reasons.
- Some refinements to the exceptions mechanism:
http://www.haskell.org/ghc/docs/4.06/users_guide/release-
notes-
406.html#exc-changes-406
http://www.haskell.org/ghc/docs/4.06/users_guide/release-4
-
06.html#exc-changes-406
- More performance tuning: compiled programs now allocate 10% less memory
than 4.04
For full details see the release notes:
http://www.haskell.org/ghc/docs/4.06/users_guide/release-
notes-
406.html
http://www.haskell.org/ghc/docs/4.06/users_guide/release-4
-
06.html
+ Mailing lists
================
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment