Book Image

Julia Programming Projects

By : Adrian Salceanu
Book Image

Julia Programming Projects

By: Adrian Salceanu

Overview of this book

Julia is a new programming language that offers a unique combination of performance and productivity. Its powerful features, friendly syntax, and speed are attracting a growing number of adopters from Python, R, and Matlab, effectively raising the bar for modern general and scientific computing. After six years in the making, Julia has reached version 1.0. Now is the perfect time to learn it, due to its large-scale adoption across a wide range of domains, including fintech, biotech, education, and AI. Beginning with an introduction to the language, Julia Programming Projects goes on to illustrate how to analyze the Iris dataset using DataFrames. You will explore functions and the type system, methods, and multiple dispatch while building a web scraper and a web app. Next, you'll delve into machine learning, where you'll build a books recommender system. You will also see how to apply unsupervised machine learning to perform clustering on the San Francisco business database. After metaprogramming, the final chapters will discuss dates and time, time series analysis, visualization, and forecasting. We'll close with package development, documenting, testing and benchmarking. By the end of the book, you will have gained the practical knowledge to build real-world applications in Julia.
Table of Contents (19 chapters)
Title Page
Copyright and Credits
About Packt

Using article types

We can refactor our code to eliminate the generic Dict data structure and represent our articles with specialized Article composite types.

Let's create a new file in our sixdegrees/ work folder, and name it Articles.jl. Edit the file by typing in the corresponding module declaration. Then, add the definition of our type and export it:

module Articles 
export Article 
struct Article 

We could've added the Article type definition to the Wikipedia.jl file, but chances are this will grow and it's better to keep them separated instead.

Another thing to note is that both the module and the type are Julia entities that are loaded in the same scope. For this reason, we can't use the name Article for both the module and the type—we'd end up with a name clash. However, the pluralized name Articles is a good name for the module, since it will encapsulate the logic for dealing with articles...