But GO BUILDING is already much more specific than any of the things in Code Compare. If you’re asking for something that specific (and comparatively uncommonly implemented), then there must be thousands of other features that would have to be compared, as well. Realistically speaking, what you’re probably going to need to do is to identify which features are important to the piece you’re designing, then do a Google search for “GO BUILDING Inform 7,” “GO BUILDING in TADS,” etc., and repeat that for each feature.
Parser-based IF has a huge possibility space, and there are many many many things that have been executed in various IF-specific languages at or above the level of the feature you’re imagining you want to compare. I do not believe that anyone has exhaustively compared all of them, even at the level of granularity that GO BUILDING implies. There are just too many things that would have to be compared, and too many systems that would have to be included in the comparison.
On the other hand, if what you’re really wondering is “which IF language should I learn in order to implement this game I’m thinking of?,” and trying to identify features of your intended game in advance that will help you make a productive decision there–then the standard answer is that the major development systems are about a wash for most people writing most types of games. Whichever system you pick will likely have some things that are somewhat easier in that development system, compared to other major options, and some things that would have been easier in other development systems will be a little more difficult. It tends to even out. There is no system that makes everything much much easier without involving some kind of trade-off; if there were, people would more or less all be using that system. That’s not to say that you might not happen to be writing a piece where it just so happens that many things might be easier in one language or another; just that “which computer language should I learn to do X?” is a subjective, complex question that’s is hard to answer without knowing the possible languages involved. It’s a specific case of the general “How do I know how to learn to do X without already knowing how to do X?” problem, which rarely has a neat solution.
But there are some Inform v. TADS comparisons out there that talk about the generalities of both languages, and the best way forward, if you’re wondering which language to learn, is to skim through some of those, use them to make the best choice possible, and then start learning one of them. If you find yourself yearning for features you heard about in the other language once you’ve started, you can always jump ship and go elsewhere.
EDIT. I meant to say more explicitly earlier that there are SOME problems that ARE clearly handled better by one system or another, or for which there are extensions or libraries or what-have-you for various development systems, and some libraries or extensions can of course be better than others. That is to say, if you’re doing a whole lot of something that falls into one of these categories, then it might be worth while to do a bit of research and see whether there’s a clear winner. So, for instance, liquid-mixing is a classic example of such a problem, which gets very complicated very quickly if you want to do anything more than the absolute basics: any development system you might consider will let you have a cup that’s full of coffee, but working in a chemistry (or alchemical) lab where the game needs to predict (say) the resulting color of a potion mixed from six different things in unequal proportions, and needing to be able to get it right, might in itself be a good reason to lean towards learning Inform 7: you can use some of Emily Short’s work on liquid-mixing. Or if your whole piece involves rock-climbing and you need a detailed, realistic implementation of a rope, you might want to look at Linus Åkesson’s emerging language Dialog, which is supposed to make these things much easier (though I have, alas, not yet poked at it and am therefore repeating gossip). Or, if you’re going to be writing a conversation-heavy game, you might want to look around at the conversation libraries available for various languages and pick a language based on which conversation library works in a way that makes sense to you. Fire is another classic examples of things that are very difficult to implement realistically once you go beyond very basic implementations, and if you’re looking for a realistic implementation of burning things, and your game works heavily with this, you might want to look around at what’s involved in simulating a realistic conflagration and how this has been done in various languages.
EDIT to edit the edit. Sigh.