Tracy Oduebo tracy-o

Big-O Time Complexities for Elixir data structures

Map [1]

Operation	Time Complexity
Access	`O(log n)`
Search	`O(log n)`
Insertion	`O(n)` for <= 32 elements, `O(log n)` for > 32 elements [2]
Deletion	`O(n)` for <= 32 elements, `O(log n)` for > 32 elements

This is way more complicated than it should be. The following conditions need to be met :

need to be able to track and merge in upstream changes
don't want remote commit messages in master
only interested in sub-directory of another repo
needs to go in a subdirectory in my repo.

In this particular case, I'm interested in bringing in the 'default' template of jsdoc as a sub-directory in my project so I could potentially make changes to the markup it genereates while also being able to update from upstream if there are changes. Ideally their template should be a separate repo added to jsdoc via a submodule -- this way I could fork it and things would be much easier.... but, it is what it is.

After much struggling with git, subtree and git-subtree, I ended up finding this http://archive.h2ik.co/2011/03/having-fun-with-git-subtree/ -- it basically sets up separate branches from tracking remote, the particular sub-directory, and uses git subtree contrib module to pull it all togther. Following are


	# execute on Mac to create services:
	docker-compose up -d

	# "login" to client container:
	docker exec -it my-docker-client sh

	# within client container:
	/ # docker ps
	CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

	const carriageReturnIndicator = "⏭️"; //WARNING: There is a regexp replace that uses this literal value.
	const spaceReplacerChar = " "; // ◽
	const pluginClassName = "speedReadingPlugin";

	function updateReadTimeEstimate(phrases, speedWPM) {
	var readTimeEstimateEl = document.getElementById("readTimeEstimate");
	readTimeEstimateEl.innerText =
	"Expected time to read the whole document at current speed: " +
	((phrases.length * 60000) / speedWPM / 1000 / 60).toFixed(1) +
	"min.";