Refactor for readability
Added more documentation, converted logical operations to (hopefully) consistent 'route' metaphor, and moved all AND(iterator, iterator) stanzas out into a single join() function that is more descriptive of what's actually happening
This commit is contained in:
parent
42aa91b77f
commit
51f5a86232
2 changed files with 116 additions and 85 deletions
|
|
@ -1,4 +1,4 @@
|
|||
// Copyright 2014 The Cayley Authors. All rights reserved.
|
||||
// Copyright 2015 The Cayley Authors. All rights reserved.
|
||||
//
|
||||
// Licensed under the Apache License, Version 2.0 (the "License");
|
||||
// you may not use this file except in compliance with the License.
|
||||
|
|
@ -140,11 +140,15 @@ func (p *Path) Except(path *Path) *Path {
|
|||
return p
|
||||
}
|
||||
|
||||
// Follow allows you to stitch two paths together. The resulting path will start
|
||||
// from where the first path left off and continue iterating down the path given
|
||||
func (p *Path) Follow(path *Path) *Path {
|
||||
p.stack = append(p.stack, followMorphism(path))
|
||||
return p
|
||||
}
|
||||
|
||||
// FollowReverse is the same as follow, except it will iterate backwards up the
|
||||
// path given as argument
|
||||
func (p *Path) FollowReverse(path *Path) *Path {
|
||||
p.stack = append(p.stack, followMorphism(path.Reverse()))
|
||||
return p
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue