You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@groovy.apache.org by gi...@apache.org on 2019/11/06 03:08:02 UTC
[groovy-dev-site] branch asf-site updated: 2019/11/06 03:07:58:
Generated dev website from groovy-website@4fc2829
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/groovy-dev-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new e9523ac 2019/11/06 03:07:58: Generated dev website from groovy-website@4fc2829
e9523ac is described below
commit e9523ac0ea5108ed602fc58312ecd140244debd4
Author: jenkins <bu...@apache.org>
AuthorDate: Wed Nov 6 03:07:58 2019 +0000
2019/11/06 03:07:58: Generated dev website from groovy-website@4fc2829
---
wiki/GEP-11.html | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/wiki/GEP-11.html b/wiki/GEP-11.html
index 89c7eed..ddcfb5b 100644
--- a/wiki/GEP-11.html
+++ b/wiki/GEP-11.html
@@ -136,7 +136,8 @@
<h2 id="_abstract_groovy_3_semantics_and_new_mop">Abstract: Groovy 3 semantics and new MOP</h2>
<div class="sectionbody">
<div class="paragraph">
-<p>For quite long we are thinking about a new MOP for Groovy, without finding the right way to do it better this time.
+<p>For some time we have been thinking about a new MOP for Groovy but haven’t been able to decide on a final
+design which mostly keeps backwards compatibility but also improves various cases that we want to improve.
It is difficult to find the right path between being user-friendly and efficient.
Thus the new MOP will contain some features the old did not, but will also remove some old features for
the sake of a more straight and more easy to understand MOP.</p>