From d3bdab6381e1b87f3d5fb6e1d1929285e522fe0a Mon Sep 17 00:00:00 2001 From: oranges Date: Mon, 23 May 2016 22:39:25 +0000 Subject: [PATCH] Revert "Add warning about list creation time at startup" GITHUB PLEASE STOP THIS This reverts commit 39a25464e65a9ec1c13e1869fa7512a6c7d72329. --- CONTRIBUTING.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 235aab71677..747a618c804 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -135,11 +135,6 @@ Copying code from one place to another maybe suitable for small short time proje Instead you can use object orientation, or simply placing repeated code in a function, to obey this specification easily. -###Startup/Runtime tradeoffs with lists -First, read lummox's comment here:http://www.byond.com/forum/?post=2086980&page=2#comment19776775 - -So, where you would normally define a list of items on the type, instead leave it null and write a proc that returns the appropriate list and check at runtime if the list is null and then define it. This offsets list creation overhead to the point where it's actually required (which for many objects, may be never at all). Remember, this tradeoff makes sense in most cases but not all, you should think carefully about your implementation before deciding. - ###No magic numbers or strings Make these #defines with a name that more clearly states what it's for.