Bugzilla – Full Text Bug Listing
| Summary: | [Xbase] Slow validator on chained method calls (with Clojures?) | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Benjamin Schwertfeger <benjamin.schwertfeger> |
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | christian.dietrich.opensource, dennis.huebner, mail, sebastian.zarnekow |
| Version: | 2.0.1 | ||
| Target Milestone: | M6 | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
| Bug Depends on: | 376037 | ||
| Bug Blocks: | |||
This does not work with a chain of .filter(typeof(String)) but with a chain of .filter(e|e!=null). I made some first improvements that will at least be a lot faster if you explicitly define the parameter types for closure arguments like in comment 0. Not 2.1 Fixed with the new TS (for valid code) Requested via bug 522520. -M. Requested via bug 522520. -M. |
I noticed in a large xtend-file, that a long line of method calls leads to very bad editing experience. The following small example leads to visible Xtext validation for seconds. If not on your machine feel free to duplicate the .map line. class Test { def test() { Collections::singleton("") .map([String e|e]) .map([String e|e]) .map([String e|e]) .map([String e|e]) .map([String e|e]) } } I had a more complex construct at office with the nighly build from 20110830, where also updating resource description took it's time.