From 6a62365a16971e3f142f69812d2cf91f008d65c8 Mon Sep 17 00:00:00 2001 From: Sami Vaarala Date: Tue, 17 Dec 2013 19:05:40 +0200 Subject: [PATCH] ditz issue update --- ...481dcf4856c1108d2ef4e17feb2b448fa3dbe.yaml | 41 +++++++++++++++++++ ...0016d7d9985d8e7bf8481d38be083787e6447.yaml | 18 ++++++++ ...ed5852b013611875149549da0780d61090132.yaml | 6 ++- ...c49e3a940f70896f13de4244e2795c2428491.yaml | 22 ++++++++++ ...f0ee555bf5930ca1ff28a27eccbaf76204471.yaml | 18 ++++++++ ...cbaa5b815598c1b60f699b62b92b622628111.yaml | 8 +++- 6 files changed, 110 insertions(+), 3 deletions(-) create mode 100644 bugs/issue-149481dcf4856c1108d2ef4e17feb2b448fa3dbe.yaml create mode 100644 bugs/issue-6e20016d7d9985d8e7bf8481d38be083787e6447.yaml create mode 100644 bugs/issue-84bc49e3a940f70896f13de4244e2795c2428491.yaml create mode 100644 bugs/issue-a59f0ee555bf5930ca1ff28a27eccbaf76204471.yaml diff --git a/bugs/issue-149481dcf4856c1108d2ef4e17feb2b448fa3dbe.yaml b/bugs/issue-149481dcf4856c1108d2ef4e17feb2b448fa3dbe.yaml new file mode 100644 index 00000000..e1eea6db --- /dev/null +++ b/bugs/issue-149481dcf4856c1108d2ef4e17feb2b448fa3dbe.yaml @@ -0,0 +1,41 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: free internal enumerator entries as soon as they've been enumerated +desc: |- + Currently the internal enumerator holds the entire enumaration sequence + until the internal enumerator is freed. Because there is no way to + enumerate a particular sequence twice, the enumerated entries could be + overwritten with e.g. "undefined" values as the enumeration proceeds, + generating string free operations steadily instead of as on massive + chunk as the enumeration finishes. +type: :task +component: duk +release: v0.9 +reporter: sva +status: :unstarted +disposition: +creation_time: 2013-12-17 11:18:51.672163 Z +references: [] + +id: 149481dcf4856c1108d2ef4e17feb2b448fa3dbe +log_events: +- - 2013-12-17 11:18:51.864087 Z + - sva + - created + - "" +- - 2013-12-17 11:19:12.792144 Z + - sva + - commented + - Update hobject-design.txt too. +- - 2013-12-17 12:45:28.370024 Z + - sva + - commented + - |- + Actually enumeration goes through the *keys* (not values) of the internal + enumerator. The keys cannot be replaced with "undefined". They could be + replaced with NULL, but this would lead to the risk of the keys being + compacted and the "_next" internal property being incorrect. + + A practical approach would be to replace each key with the empty string as + soon as it was enumerated. This would create duplicate keys in the entry + part, however, something that is not normally allowed so it would need + careful consideration. diff --git a/bugs/issue-6e20016d7d9985d8e7bf8481d38be083787e6447.yaml b/bugs/issue-6e20016d7d9985d8e7bf8481d38be083787e6447.yaml new file mode 100644 index 00000000..b71d6d13 --- /dev/null +++ b/bugs/issue-6e20016d7d9985d8e7bf8481d38be083787e6447.yaml @@ -0,0 +1,18 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: "function instance optimization: prototype object, often not needed but mandatory" +desc: "" +type: :task +component: duk +release: v0.10 +reporter: sva +status: :unstarted +disposition: +creation_time: 2013-12-17 13:43:21.717741 Z +references: [] + +id: 6e20016d7d9985d8e7bf8481d38be083787e6447 +log_events: +- - 2013-12-17 13:43:21.921805 Z + - sva + - created + - "" diff --git a/bugs/issue-740ed5852b013611875149549da0780d61090132.yaml b/bugs/issue-740ed5852b013611875149549da0780d61090132.yaml index a374c666..7b34964f 100644 --- a/bugs/issue-740ed5852b013611875149549da0780d61090132.yaml +++ b/bugs/issue-740ed5852b013611875149549da0780d61090132.yaml @@ -5,7 +5,7 @@ desc: |- reverse, sort?). type: :task component: duk -release: +release: v0.10 reporter: sva status: :unstarted disposition: @@ -18,3 +18,7 @@ log_events: - sva - created - "" +- - 2013-12-17 11:03:46.144583 Z + - sva + - assigned to release v0.10 from unassigned + - "" diff --git a/bugs/issue-84bc49e3a940f70896f13de4244e2795c2428491.yaml b/bugs/issue-84bc49e3a940f70896f13de4244e2795c2428491.yaml new file mode 100644 index 00000000..ee752a6f --- /dev/null +++ b/bugs/issue-84bc49e3a940f70896f13de4244e2795c2428491.yaml @@ -0,0 +1,22 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: performance note on enumeration vs. looping array indices +desc: "" +type: :task +component: duk +release: v0.8 +reporter: sva +status: :closed +disposition: :fixed +creation_time: 2013-12-17 11:19:44.519810 Z +references: [] + +id: 84bc49e3a940f70896f13de4244e2795c2428491 +log_events: +- - 2013-12-17 11:19:44.679779 Z + - sva + - created + - "" +- - 2013-12-17 14:57:39.859993 Z + - sva + - closed with disposition fixed + - "" diff --git a/bugs/issue-a59f0ee555bf5930ca1ff28a27eccbaf76204471.yaml b/bugs/issue-a59f0ee555bf5930ca1ff28a27eccbaf76204471.yaml new file mode 100644 index 00000000..5c09ac0e --- /dev/null +++ b/bugs/issue-a59f0ee555bf5930ca1ff28a27eccbaf76204471.yaml @@ -0,0 +1,18 @@ +--- !ditz.rubyforge.org,2008-03-06/issue +title: "function instance optimization: caller, arguments properties" +desc: Make them virtual / autospawned? +type: :task +component: duk +release: v0.10 +reporter: sva +status: :unstarted +disposition: +creation_time: 2013-12-17 13:43:00.184527 Z +references: [] + +id: a59f0ee555bf5930ca1ff28a27eccbaf76204471 +log_events: +- - 2013-12-17 13:43:00.396680 Z + - sva + - created + - "" diff --git a/bugs/issue-d44cbaa5b815598c1b60f699b62b92b622628111.yaml b/bugs/issue-d44cbaa5b815598c1b60f699b62b92b622628111.yaml index 3329622c..740eafe5 100644 --- a/bugs/issue-d44cbaa5b815598c1b60f699b62b92b622628111.yaml +++ b/bugs/issue-d44cbaa5b815598c1b60f699b62b92b622628111.yaml @@ -5,8 +5,8 @@ type: :task component: duk release: v0.8 reporter: sva -status: :unstarted -disposition: +status: :closed +disposition: :fixed creation_time: 2013-12-13 23:48:58.893865 Z references: [] @@ -16,3 +16,7 @@ log_events: - sva - created - "" +- - 2013-12-17 16:55:43.172105 Z + - sva + - closed with disposition fixed + - ""