WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:16.529 align:start position:0% [Music] 00:00:16.529 --> 00:00:16.539 align:start position:0% [Music] 00:00:16.539 --> 00:00:20.290 align:start position:0% [Music] yeah<00:00:17.539> hello<00:00:17.990> everyone<00:00:18.790> so<00:00:19.790> I'm<00:00:19.880> going<00:00:20.060> to<00:00:20.090> talk 00:00:20.290 --> 00:00:20.300 align:start position:0% yeah hello everyone so I'm going to talk 00:00:20.300 --> 00:00:22.840 align:start position:0% yeah hello everyone so I'm going to talk about<00:00:20.450> Julia<00:00:20.980> which<00:00:21.980> is<00:00:22.160> an<00:00:22.310> intermediate 00:00:22.840 --> 00:00:22.850 align:start position:0% about Julia which is an intermediate 00:00:22.850 --> 00:00:24.910 align:start position:0% about Julia which is an intermediate representation<00:00:23.630> or<00:00:23.840> an<00:00:24.170> intermediate 00:00:24.910 --> 00:00:24.920 align:start position:0% representation or an intermediate 00:00:24.920 --> 00:00:29.200 align:start position:0% representation or an intermediate language<00:00:25.090> for<00:00:26.090> ATM<00:00:26.510> contracts<00:00:28.180> you<00:00:29.180> know 00:00:29.200 --> 00:00:29.210 align:start position:0% language for ATM contracts you know 00:00:29.210 --> 00:00:31.090 align:start position:0% language for ATM contracts you know let's<00:00:29.480> just<00:00:29.570> first<00:00:29.840> see<00:00:30.110> what<00:00:30.800> are<00:00:30.950> the 00:00:31.090 --> 00:00:31.100 align:start position:0% let's just first see what are the 00:00:31.100 --> 00:00:33.400 align:start position:0% let's just first see what are the problems<00:00:31.550> why<00:00:31.789> would<00:00:32.210> we<00:00:32.360> need<00:00:32.599> a<00:00:32.840> new 00:00:33.400 --> 00:00:33.410 align:start position:0% problems why would we need a new 00:00:33.410 --> 00:00:35.530 align:start position:0% problems why would we need a new language<00:00:33.590> or<00:00:34.160> am<00:00:34.550> I<00:00:34.640> just<00:00:34.670> crazy<00:00:34.970> that<00:00:35.240> we<00:00:35.420> need 00:00:35.530 --> 00:00:35.540 align:start position:0% language or am I just crazy that we need 00:00:35.540 --> 00:00:39.310 align:start position:0% language or am I just crazy that we need a<00:00:35.570> new<00:00:35.750> language<00:00:37.540> in<00:00:38.540> fact<00:00:38.810> we<00:00:38.990> do<00:00:39.140> have<00:00:39.290> a 00:00:39.310 --> 00:00:39.320 align:start position:0% a new language in fact we do have a 00:00:39.320 --> 00:00:41.140 align:start position:0% a new language in fact we do have a couple<00:00:39.500> of<00:00:39.680> problems<00:00:39.920> and<00:00:40.340> most<00:00:40.940> of<00:00:41.060> these 00:00:41.140 --> 00:00:41.150 align:start position:0% couple of problems and most of these 00:00:41.150 --> 00:00:43.030 align:start position:0% couple of problems and most of these problems<00:00:41.450> actually<00:00:42.170> related<00:00:42.800> to<00:00:42.950> the 00:00:43.030 --> 00:00:43.040 align:start position:0% problems actually related to the 00:00:43.040 --> 00:00:45.729 align:start position:0% problems actually related to the solidity<00:00:43.400> compiler<00:00:43.910> itself<00:00:44.560> the<00:00:45.560> first 00:00:45.729 --> 00:00:45.739 align:start position:0% solidity compiler itself the first 00:00:45.739 --> 00:00:48.580 align:start position:0% solidity compiler itself the first problem<00:00:46.160> is<00:00:46.310> you<00:00:46.970> know<00:00:47.060> auditing<00:00:47.600> contracts 00:00:48.580 --> 00:00:48.590 align:start position:0% problem is you know auditing contracts 00:00:48.590 --> 00:00:51.460 align:start position:0% problem is you know auditing contracts written<00:00:49.010> in<00:00:49.280> solidity<00:00:49.670> is<00:00:50.000> not<00:00:50.600> that<00:00:50.810> simple<00:00:51.050> I 00:00:51.460 --> 00:00:51.470 align:start position:0% written in solidity is not that simple I 00:00:51.470 --> 00:00:54.790 align:start position:0% written in solidity is not that simple I will<00:00:51.800> explain<00:00:52.190> that<00:00:52.250> in<00:00:52.430> a<00:00:52.579> bit<00:00:53.290> then<00:00:54.320> the 00:00:54.790 --> 00:00:54.800 align:start position:0% will explain that in a bit then the 00:00:54.800 --> 00:00:57.700 align:start position:0% will explain that in a bit then the solidity<00:00:55.220> compiler<00:00:55.670> is<00:00:55.880> written<00:00:56.210> in<00:00:56.300> C++<00:00:56.710> and 00:00:57.700 --> 00:00:57.710 align:start position:0% solidity compiler is written in C++ and 00:00:57.710 --> 00:01:00.430 align:start position:0% solidity compiler is written in C++ and a<00:00:57.980> lot<00:00:58.100> of<00:00:58.220> things<00:00:58.489> a<00:00:58.820> lot<00:00:58.850> of<00:00:59.390> helpers<00:00:59.960> lot<00:01:00.320> of 00:01:00.430 --> 00:01:00.440 align:start position:0% a lot of things a lot of helpers lot of 00:01:00.440 --> 00:01:02.590 align:start position:0% a lot of things a lot of helpers lot of code<00:01:01.070> generators<00:01:01.700> are<00:01:02.090> of<00:01:02.210> course<00:01:02.420> between 00:01:02.590 --> 00:01:02.600 align:start position:0% code generators are of course between 00:01:02.600 --> 00:01:05.860 align:start position:0% code generators are of course between C++<00:01:03.380> and<00:01:03.590> they<00:01:04.009> are<00:01:04.129> quite<00:01:04.640> complex<00:01:05.119> and<00:01:05.780> you 00:01:05.860 --> 00:01:05.870 align:start position:0% C++ and they are quite complex and you 00:01:05.870 --> 00:01:07.630 align:start position:0% C++ and they are quite complex and you know<00:01:05.930> with<00:01:06.080> time<00:01:06.229> they<00:01:06.409> can<00:01:06.620> become<00:01:06.770> even<00:01:07.610> more 00:01:07.630 --> 00:01:07.640 align:start position:0% know with time they can become even more 00:01:07.640 --> 00:01:10.870 align:start position:0% know with time they can become even more complex<00:01:08.210> as<00:01:08.330> more<00:01:08.510> features<00:01:08.960> are<00:01:09.200> added<00:01:09.880> the 00:01:10.870 --> 00:01:10.880 align:start position:0% complex as more features are added the 00:01:10.880 --> 00:01:13.780 align:start position:0% complex as more features are added the next<00:01:11.120> problem<00:01:11.299> is<00:01:11.979> optimizations<00:01:12.979> you<00:01:13.670> know 00:01:13.780 --> 00:01:13.790 align:start position:0% next problem is optimizations you know 00:01:13.790 --> 00:01:16.270 align:start position:0% next problem is optimizations you know different<00:01:14.090> optimization<00:01:14.750> steps<00:01:15.080> on<00:01:15.500> the 00:01:16.270 --> 00:01:16.280 align:start position:0% different optimization steps on the 00:01:16.280 --> 00:01:18.820 align:start position:0% different optimization steps on the compilation<00:01:16.580> that<00:01:17.510> can<00:01:17.750> become<00:01:17.930> very<00:01:18.470> complex 00:01:18.820 --> 00:01:18.830 align:start position:0% compilation that can become very complex 00:01:18.830 --> 00:01:23.350 align:start position:0% compilation that can become very complex as<00:01:19.010> well<00:01:20.710> this<00:01:21.710> one<00:01:21.950> so<00:01:22.490> far<00:01:22.520> hasn't<00:01:22.970> been<00:01:23.240> an 00:01:23.350 --> 00:01:23.360 align:start position:0% as well this one so far hasn't been an 00:01:23.360 --> 00:01:26.260 align:start position:0% as well this one so far hasn't been an issue<00:01:23.510> because<00:01:23.900> solidity<00:01:24.560> can<00:01:25.369> only<00:01:25.640> output 00:01:26.260 --> 00:01:26.270 align:start position:0% issue because solidity can only output 00:01:26.270 --> 00:01:29.050 align:start position:0% issue because solidity can only output evm<00:01:27.020> bytecode<00:01:27.560> but<00:01:28.400> you<00:01:28.520> know<00:01:28.610> in<00:01:28.700> the<00:01:28.790> feech 00:01:29.050 --> 00:01:29.060 align:start position:0% evm bytecode but you know in the feech 00:01:29.060 --> 00:01:32.350 align:start position:0% evm bytecode but you know in the feech future<00:01:29.869> we<00:01:30.320> might<00:01:30.530> move<00:01:30.680> on<00:01:30.860> to<00:01:31.070> new<00:01:31.880> virtual 00:01:32.350 --> 00:01:32.360 align:start position:0% future we might move on to new virtual 00:01:32.360 --> 00:01:35.050 align:start position:0% future we might move on to new virtual machines<00:01:32.840> so<00:01:33.049> one<00:01:33.950> such<00:01:34.189> virtual<00:01:34.549> machine<00:01:34.820> is 00:01:35.050 --> 00:01:35.060 align:start position:0% machines so one such virtual machine is 00:01:35.060 --> 00:01:37.750 align:start position:0% machines so one such virtual machine is called<00:01:35.330> a<00:01:35.570> vm<00:01:35.810> 1.5<00:01:36.500> and<00:01:36.830> that<00:01:37.430> one<00:01:37.580> is<00:01:37.670> called 00:01:37.750 --> 00:01:37.760 align:start position:0% called a vm 1.5 and that one is called 00:01:37.760 --> 00:01:40.510 align:start position:0% called a vm 1.5 and that one is called it<00:01:38.119> wasn't<00:01:38.540> in<00:01:39.350> the<00:01:39.439> current<00:01:39.770> state<00:01:40.490> of 00:01:40.510 --> 00:01:40.520 align:start position:0% it wasn't in the current state of 00:01:40.520 --> 00:01:43.240 align:start position:0% it wasn't in the current state of solidity<00:01:41.320> there<00:01:42.320> would<00:01:42.500> be<00:01:42.530> a<00:01:42.650> quiet<00:01:42.950> big 00:01:43.240 --> 00:01:43.250 align:start position:0% solidity there would be a quiet big 00:01:43.250 --> 00:01:44.649 align:start position:0% solidity there would be a quiet big change<00:01:43.610> to<00:01:43.850> rewrite<00:01:44.150> the<00:01:44.299> compiler 00:01:44.649 --> 00:01:44.659 align:start position:0% change to rewrite the compiler 00:01:44.659 --> 00:01:48.700 align:start position:0% change to rewrite the compiler supporting<00:01:45.439> any<00:01:45.799> of<00:01:45.950> those<00:01:46.210> and<00:01:47.710> lastly 00:01:48.700 --> 00:01:48.710 align:start position:0% supporting any of those and lastly 00:01:48.710 --> 00:01:50.789 align:start position:0% supporting any of those and lastly creating<00:01:49.250> the<00:01:49.520> cells<00:01:49.909> or<00:01:50.330> domain-specific 00:01:50.789 --> 00:01:50.799 align:start position:0% creating the cells or domain-specific 00:01:50.799 --> 00:01:54.190 align:start position:0% creating the cells or domain-specific languages<00:01:51.850> it<00:01:52.850> doesn't<00:01:53.360> really<00:01:53.479> exist<00:01:53.659> at<00:01:54.049> the 00:01:54.190 --> 00:01:54.200 align:start position:0% languages it doesn't really exist at the 00:01:54.200 --> 00:01:56.920 align:start position:0% languages it doesn't really exist at the moment<00:01:54.530> and<00:01:54.820> the<00:01:55.820> most<00:01:56.060> practical<00:01:56.570> way<00:01:56.600> to<00:01:56.689> do 00:01:56.920 --> 00:01:56.930 align:start position:0% moment and the most practical way to do 00:01:56.930 --> 00:01:59.170 align:start position:0% moment and the most practical way to do that<00:01:57.110> is<00:01:57.340> to<00:01:58.340> compile<00:01:58.700> a<00:01:58.729> domain-specific 00:01:59.170 --> 00:01:59.180 align:start position:0% that is to compile a domain-specific 00:01:59.180 --> 00:02:03.280 align:start position:0% that is to compile a domain-specific language<00:01:59.960> -<00:02:00.560> solidity<00:02:01.009> or<00:02:01.640> -<00:02:01.880> serpent<00:02:02.329> and<00:02:02.659> by 00:02:03.280 --> 00:02:03.290 align:start position:0% language - solidity or - serpent and by 00:02:03.290 --> 00:02:04.929 align:start position:0% language - solidity or - serpent and by doing<00:02:03.470> that<00:02:03.590> you<00:02:04.070> will<00:02:04.189> be<00:02:04.340> exposed<00:02:04.549> to<00:02:04.820> the 00:02:04.929 --> 00:02:04.939 align:start position:0% doing that you will be exposed to the 00:02:04.939 --> 00:02:07.420 align:start position:0% doing that you will be exposed to the very<00:02:05.030> same<00:02:05.329> problems<00:02:05.810> solidity<00:02:06.710> is<00:02:06.829> exposed 00:02:07.420 --> 00:02:07.430 align:start position:0% very same problems solidity is exposed 00:02:07.430 --> 00:02:11.140 align:start position:0% very same problems solidity is exposed to<00:02:08.649> so<00:02:09.649> this<00:02:09.890> is<00:02:09.950> one<00:02:10.280> of<00:02:10.310> the<00:02:10.520> example<00:02:10.970> for 00:02:11.140 --> 00:02:11.150 align:start position:0% to so this is one of the example for 00:02:11.150 --> 00:02:13.839 align:start position:0% to so this is one of the example for auditing<00:02:11.750> right<00:02:12.709> the<00:02:13.099> multiple<00:02:13.489> parts<00:02:13.730> do 00:02:13.839 --> 00:02:13.849 align:start position:0% auditing right the multiple parts do 00:02:13.849 --> 00:02:14.890 align:start position:0% auditing right the multiple parts do auditing 00:02:14.890 --> 00:02:14.900 align:start position:0% auditing 00:02:14.900 --> 00:02:17.080 align:start position:0% auditing before<00:02:15.230> one<00:02:15.739> needs<00:02:15.890> to<00:02:16.040> make<00:02:16.129> sure<00:02:16.189> that<00:02:17.030> the 00:02:17.080 --> 00:02:17.090 align:start position:0% before one needs to make sure that the 00:02:17.090 --> 00:02:19.539 align:start position:0% before one needs to make sure that the contract<00:02:17.540> written<00:02:17.659> solidity<00:02:18.260> does<00:02:19.099> what<00:02:19.519> a 00:02:19.539 --> 00:02:19.549 align:start position:0% contract written solidity does what a 00:02:19.549 --> 00:02:22.089 align:start position:0% contract written solidity does what a functional<00:02:19.970> specification<00:02:20.120> says<00:02:20.989> in<00:02:21.379> this 00:02:22.089 --> 00:02:22.099 align:start position:0% functional specification says in this 00:02:22.099 --> 00:02:26.289 align:start position:0% functional specification says in this case<00:02:22.569> the<00:02:23.569> intention<00:02:24.019> was<00:02:24.230> to<00:02:24.790> being<00:02:25.790> able<00:02:26.060> to 00:02:26.289 --> 00:02:26.299 align:start position:0% case the intention was to being able to 00:02:26.299 --> 00:02:28.809 align:start position:0% case the intention was to being able to redeem<00:02:26.569> the<00:02:27.049> money<00:02:27.230> once<00:02:27.500> but<00:02:28.370> I<00:02:28.400> don't<00:02:28.519> think 00:02:28.809 --> 00:02:28.819 align:start position:0% redeem the money once but I don't think 00:02:28.819 --> 00:02:32.020 align:start position:0% redeem the money once but I don't think the<00:02:28.970> contract<00:02:29.360> does<00:02:29.510> did<00:02:30.519> the<00:02:31.519> second<00:02:31.879> problem 00:02:32.020 --> 00:02:32.030 align:start position:0% the contract does did the second problem 00:02:32.030 --> 00:02:34.300 align:start position:0% the contract does did the second problem with<00:02:32.239> auditing<00:02:32.750> which<00:02:33.560> might<00:02:33.769> not<00:02:33.859> be<00:02:33.920> done<00:02:34.159> in 00:02:34.300 --> 00:02:34.310 align:start position:0% with auditing which might not be done in 00:02:34.310 --> 00:02:37.330 align:start position:0% with auditing which might not be done in every<00:02:34.430> single<00:02:34.849> case<00:02:35.120> is<00:02:36.010> verifying<00:02:37.010> that<00:02:37.129> the 00:02:37.330 --> 00:02:37.340 align:start position:0% every single case is verifying that the 00:02:37.340 --> 00:02:40.599 align:start position:0% every single case is verifying that the compiler<00:02:37.790> creates<00:02:38.569> byte<00:02:39.019> code<00:02:39.609> accordingly 00:02:40.599 --> 00:02:40.609 align:start position:0% compiler creates byte code accordingly 00:02:40.609 --> 00:02:43.539 align:start position:0% compiler creates byte code accordingly to<00:02:41.390> the<00:02:41.510> source<00:02:41.720> code<00:02:42.250> so<00:02:43.250> there<00:02:43.400> are<00:02:43.459> two 00:02:43.539 --> 00:02:43.549 align:start position:0% to the source code so there are two 00:02:43.549 --> 00:02:47.410 align:start position:0% to the source code so there are two examples<00:02:44.060> there<00:02:44.269> the<00:02:44.900> top<00:02:45.079> one<00:02:45.319> is<00:02:45.500> a<00:02:46.420> assembly 00:02:47.410 --> 00:02:47.420 align:start position:0% examples there the top one is a assembly 00:02:47.420 --> 00:02:51.849 align:start position:0% examples there the top one is a assembly call<00:02:47.720> in<00:02:47.959> functional<00:02:50.019> representation<00:02:51.019> so 00:02:51.849 --> 00:02:51.859 align:start position:0% call in functional representation so 00:02:51.859 --> 00:02:54.699 align:start position:0% call in functional representation so functional<00:02:52.310> inline<00:02:52.609> assembly<00:02:53.060> and<00:02:53.659> there<00:02:54.590> you 00:02:54.699 --> 00:02:54.709 align:start position:0% functional inline assembly and there you 00:02:54.709 --> 00:02:57.550 align:start position:0% functional inline assembly and there you see<00:02:54.950> four<00:02:55.340> variables<00:02:55.879> in<00:02:56.090> the<00:02:56.209> call<00:02:56.420> that<00:02:57.409> is 00:02:57.550 --> 00:02:57.560 align:start position:0% see four variables in the call that is 00:02:57.560 --> 00:03:00.670 align:start position:0% see four variables in the call that is quite<00:02:57.799> readable<00:02:58.150> in<00:02:59.150> the<00:02:59.329> bottom<00:02:59.629> there<00:03:00.500> is 00:03:00.670 --> 00:03:00.680 align:start position:0% quite readable in the bottom there is 00:03:00.680 --> 00:03:04.569 align:start position:0% quite readable in the bottom there is the<00:03:01.010> EVM<00:03:01.400> byte<00:03:01.639> code<00:03:01.909> counterpart<00:03:02.569> and<00:03:03.579> it 00:03:04.569 --> 00:03:04.579 align:start position:0% the EVM byte code counterpart and it 00:03:04.579 --> 00:03:06.789 align:start position:0% the EVM byte code counterpart and it doesn't<00:03:04.879> really<00:03:05.060> look<00:03:05.359> readable<00:03:05.840> the<00:03:06.439> tone<00:03:06.650> of 00:03:06.789 --> 00:03:06.799 align:start position:0% doesn't really look readable the tone of 00:03:06.799 --> 00:03:09.339 align:start position:0% doesn't really look readable the tone of swaps<00:03:07.159> and<00:03:07.370> dupes<00:03:07.609> the<00:03:08.480> reason<00:03:08.810> for<00:03:08.959> that<00:03:09.019> is 00:03:09.339 --> 00:03:09.349 align:start position:0% swaps and dupes the reason for that is 00:03:09.349 --> 00:03:13.839 align:start position:0% swaps and dupes the reason for that is in<00:03:09.730> solidity<00:03:10.730> every<00:03:11.569> variable<00:03:12.139> is<00:03:12.579> as<00:03:13.579> a<00:03:13.639> life 00:03:13.839 --> 00:03:13.849 align:start position:0% in solidity every variable is as a life 00:03:13.849 --> 00:03:16.479 align:start position:0% in solidity every variable is as a life cycle<00:03:14.090> of<00:03:14.480> existence<00:03:14.750> until<00:03:15.590> the<00:03:16.159> end<00:03:16.280> of<00:03:16.340> the 00:03:16.479 --> 00:03:16.489 align:start position:0% cycle of existence until the end of the 00:03:16.489 --> 00:03:19.330 align:start position:0% cycle of existence until the end of the block<00:03:16.689> so<00:03:17.689> in<00:03:17.780> that<00:03:17.900> case<00:03:18.170> there<00:03:18.470> they<00:03:19.129> still 00:03:19.330 --> 00:03:19.340 align:start position:0% block so in that case there they still 00:03:19.340 --> 00:03:22.030 align:start position:0% block so in that case there they still exist<00:03:19.790> after<00:03:20.239> the<00:03:20.510> call<00:03:20.780> so<00:03:21.500> they<00:03:21.620> have<00:03:21.859> to<00:03:21.949> be 00:03:22.030 --> 00:03:22.040 align:start position:0% exist after the call so they have to be 00:03:22.040 --> 00:03:24.400 align:start position:0% exist after the call so they have to be kept<00:03:22.310> on<00:03:22.459> the<00:03:22.579> stack<00:03:22.879> and<00:03:23.139> therefore<00:03:24.139> we<00:03:24.260> need 00:03:24.400 --> 00:03:24.410 align:start position:0% kept on the stack and therefore we need 00:03:24.410 --> 00:03:26.259 align:start position:0% kept on the stack and therefore we need to<00:03:24.440> swap<00:03:24.739> them<00:03:24.919> around<00:03:25.030> ability<00:03:26.030> to<00:03:26.150> make 00:03:26.259 --> 00:03:26.269 align:start position:0% to swap them around ability to make 00:03:26.269 --> 00:03:28.990 align:start position:0% to swap them around ability to make duplications<00:03:26.900> of<00:03:27.079> them<00:03:27.260> I<00:03:27.730> guess<00:03:28.730> you<00:03:28.849> can 00:03:28.990 --> 00:03:29.000 align:start position:0% duplications of them I guess you can 00:03:29.000 --> 00:03:30.640 align:start position:0% duplications of them I guess you can agree<00:03:29.150> that<00:03:29.269> it's<00:03:29.540> quite<00:03:29.720> hard<00:03:29.750> to<00:03:30.530> verify 00:03:30.640 --> 00:03:30.650 align:start position:0% agree that it's quite hard to verify 00:03:30.650 --> 00:03:34.210 align:start position:0% agree that it's quite hard to verify that<00:03:31.400> even<00:03:31.669> byte<00:03:31.909> code<00:03:32.500> actually<00:03:33.500> corresponds 00:03:34.210 --> 00:03:34.220 align:start position:0% that even byte code actually corresponds 00:03:34.220 --> 00:03:38.589 align:start position:0% that even byte code actually corresponds to<00:03:34.310> that<00:03:34.489> assembly<00:03:36.790> and<00:03:37.790> these<00:03:37.970> are<00:03:38.150> this<00:03:38.449> is 00:03:38.589 --> 00:03:38.599 align:start position:0% to that assembly and these are this is 00:03:38.599 --> 00:03:42.339 align:start position:0% to that assembly and these are this is one<00:03:38.750> example<00:03:38.870> for<00:03:39.290> helpers<00:03:40.840> this<00:03:41.840> actually<00:03:42.230> is 00:03:42.339 --> 00:03:42.349 align:start position:0% one example for helpers this actually is 00:03:42.349 --> 00:03:47.009 align:start position:0% one example for helpers this actually is the<00:03:42.709> code<00:03:43.310> for<00:03:44.109> pushing<00:03:45.109> a<00:03:45.229> value<00:03:45.530> to<00:03:45.709> an<00:03:45.769> array 00:03:47.009 --> 00:03:47.019 align:start position:0% the code for pushing a value to an array 00:03:47.019 --> 00:03:49.869 align:start position:0% the code for pushing a value to an array first<00:03:48.019> we<00:03:48.199> retrieve<00:03:48.620> the<00:03:48.739> length<00:03:48.949> we<00:03:49.489> increase 00:03:49.869 --> 00:03:49.879 align:start position:0% first we retrieve the length we increase 00:03:49.879 --> 00:03:52.149 align:start position:0% first we retrieve the length we increase the<00:03:50.060> length<00:03:50.209> of<00:03:50.419> the<00:03:50.540> array<00:03:50.750> we<00:03:51.440> resize<00:03:51.859> it 00:03:52.149 --> 00:03:52.159 align:start position:0% the length of the array we resize it 00:03:52.159 --> 00:03:55.300 align:start position:0% the length of the array we resize it then<00:03:53.150> we<00:03:53.389> get<00:03:53.629> to<00:03:53.780> reference<00:03:54.260> in<00:03:54.620> this<00:03:54.979> example 00:03:55.300 --> 00:03:55.310 align:start position:0% then we get to reference in this example 00:03:55.310 --> 00:03:57.879 align:start position:0% then we get to reference in this example we<00:03:55.489> get<00:03:55.579> to<00:03:55.729> reference<00:03:56.180> of<00:03:56.419> a<00:03:56.870> storage<00:03:57.560> slot 00:03:57.879 --> 00:03:57.889 align:start position:0% we get to reference of a storage slot 00:03:57.889 --> 00:04:00.879 align:start position:0% we get to reference of a storage slot and<00:03:58.250> a<00:03:58.790> storage<00:03:58.970> offset<00:03:59.449> and<00:04:00.169> then<00:04:00.319> finally<00:04:00.769> we 00:04:00.879 --> 00:04:00.889 align:start position:0% and a storage offset and then finally we 00:04:00.889 --> 00:04:05.559 align:start position:0% and a storage offset and then finally we can<00:04:01.040> interact<00:04:01.629> with<00:04:02.629> that<00:04:02.720> array<00:04:04.299> so<00:04:05.299> there 00:04:05.559 --> 00:04:05.569 align:start position:0% can interact with that array so there 00:04:05.569 --> 00:04:09.099 align:start position:0% can interact with that array so there must<00:04:05.750> be<00:04:05.930> a<00:04:05.959> way<00:04:06.169> to<00:04:06.229> improve<00:04:06.859> this<00:04:08.049> let's<00:04:09.049> just 00:04:09.099 --> 00:04:09.109 align:start position:0% must be a way to improve this let's just 00:04:09.109 --> 00:04:10.869 align:start position:0% must be a way to improve this let's just take<00:04:09.319> a<00:04:09.349> step<00:04:09.470> back<00:04:09.829> and<00:04:10.159> look<00:04:10.669> at<00:04:10.790> other 00:04:10.869 --> 00:04:10.879 align:start position:0% take a step back and look at other 00:04:10.879 --> 00:04:13.330 align:start position:0% take a step back and look at other compilers<00:04:11.530> you<00:04:12.530> know<00:04:12.650> outside<00:04:12.829> of<00:04:13.099> the 00:04:13.330 --> 00:04:13.340 align:start position:0% compilers you know outside of the 00:04:13.340 --> 00:04:18.300 align:start position:0% compilers you know outside of the etherium<00:04:14.739> so<00:04:15.739> basically<00:04:16.070> for<00:04:16.820> many<00:04:17.389> years 00:04:18.300 --> 00:04:18.310 align:start position:0% etherium so basically for many years 00:04:18.310 --> 00:04:21.099 align:start position:0% etherium so basically for many years compilers<00:04:19.310> traditional<00:04:20.090> compilers<00:04:20.539> have 00:04:21.099 --> 00:04:21.109 align:start position:0% compilers traditional compilers have 00:04:21.109 --> 00:04:23.230 align:start position:0% compilers traditional compilers have been<00:04:21.260> working<00:04:21.650> in<00:04:21.739> different<00:04:22.039> stages<00:04:22.280> the 00:04:23.230 --> 00:04:23.240 align:start position:0% been working in different stages the 00:04:23.240 --> 00:04:25.029 align:start position:0% been working in different stages the first<00:04:23.270> stage<00:04:23.539> is<00:04:23.900> the<00:04:24.020> front<00:04:24.260> end<00:04:24.500> which 00:04:25.029 --> 00:04:25.039 align:start position:0% first stage is the front end which 00:04:25.039 --> 00:04:27.580 align:start position:0% first stage is the front end which parses<00:04:25.279> the<00:04:25.550> source<00:04:25.760> code<00:04:26.060> does 00:04:27.580 --> 00:04:27.590 align:start position:0% parses the source code does 00:04:27.590 --> 00:04:29.920 align:start position:0% parses the source code does let's<00:04:28.010> check<00:04:28.190> several<00:04:28.430> things<00:04:28.790> and<00:04:29.120> finally 00:04:29.920 --> 00:04:29.930 align:start position:0% let's check several things and finally 00:04:29.930 --> 00:04:31.810 align:start position:0% let's check several things and finally creates<00:04:30.800> an<00:04:30.919> intermediate<00:04:31.460> representation 00:04:31.810 --> 00:04:31.820 align:start position:0% creates an intermediate representation 00:04:31.820 --> 00:04:35.770 align:start position:0% creates an intermediate representation of<00:04:32.360> the<00:04:33.320> program<00:04:34.090> the<00:04:35.090> next<00:04:35.270> stage<00:04:35.540> is<00:04:35.750> the 00:04:35.770 --> 00:04:35.780 align:start position:0% of the program the next stage is the 00:04:35.780 --> 00:04:37.530 align:start position:0% of the program the next stage is the middle<00:04:36.110> end<00:04:36.260> which<00:04:36.889> can<00:04:36.919> apply<00:04:37.340> different 00:04:37.530 --> 00:04:37.540 align:start position:0% middle end which can apply different 00:04:37.540 --> 00:04:40.180 align:start position:0% middle end which can apply different optimizations<00:04:38.540> on<00:04:38.780> the<00:04:39.080> front<00:04:39.290> on<00:04:39.800> the 00:04:40.180 --> 00:04:40.190 align:start position:0% optimizations on the front on the 00:04:40.190 --> 00:04:43.210 align:start position:0% optimizations on the front on the intermediate<00:04:41.000> representation<00:04:41.830> and<00:04:42.830> the<00:04:43.100> last 00:04:43.210 --> 00:04:43.220 align:start position:0% intermediate representation and the last 00:04:43.220 --> 00:04:45.129 align:start position:0% intermediate representation and the last one<00:04:43.340> is<00:04:43.430> the<00:04:43.550> back<00:04:43.699> end<00:04:43.940> of<00:04:44.060> course<00:04:44.570> which 00:04:45.129 --> 00:04:45.139 align:start position:0% one is the back end of course which 00:04:45.139 --> 00:04:47.530 align:start position:0% one is the back end of course which generates<00:04:46.130> bytecode<00:04:46.639> for<00:04:47.180> the<00:04:47.270> target 00:04:47.530 --> 00:04:47.540 align:start position:0% generates bytecode for the target 00:04:47.540 --> 00:04:49.450 align:start position:0% generates bytecode for the target machine<00:04:47.690> and<00:04:48.110> again<00:04:48.770> it<00:04:49.100> can<00:04:49.280> do 00:04:49.450 --> 00:04:49.460 align:start position:0% machine and again it can do 00:04:49.460 --> 00:04:52.800 align:start position:0% machine and again it can do optimizations<00:04:50.090> there<00:04:51.340> compared<00:04:52.340> to<00:04:52.460> debt 00:04:52.800 --> 00:04:52.810 align:start position:0% optimizations there compared to debt 00:04:52.810 --> 00:04:55.510 align:start position:0% optimizations there compared to debt solidity<00:04:53.810> only<00:04:54.080> has<00:04:54.199> two<00:04:54.410> stages<00:04:54.680> were<00:04:55.340> more 00:04:55.510 --> 00:04:55.520 align:start position:0% solidity only has two stages were more 00:04:55.520 --> 00:04:58.480 align:start position:0% solidity only has two stages were more like<00:04:55.699> 1.5<00:04:55.970> stages<00:04:56.960> there's<00:04:57.889> one<00:04:58.040> stage<00:04:58.280> which 00:04:58.480 --> 00:04:58.490 align:start position:0% like 1.5 stages there's one stage which 00:04:58.490 --> 00:05:00.909 align:start position:0% like 1.5 stages there's one stage which does<00:04:58.729> everything<00:04:58.900> and<00:04:59.900> there's<00:05:00.500> another<00:05:00.680> one 00:05:00.909 --> 00:05:00.919 align:start position:0% does everything and there's another one 00:05:00.919 --> 00:05:03.400 align:start position:0% does everything and there's another one which<00:05:01.130> optimizes<00:05:01.310> evm<00:05:01.970> bytecode<00:05:02.419> at<00:05:03.229> this 00:05:03.400 --> 00:05:03.410 align:start position:0% which optimizes evm bytecode at this 00:05:03.410 --> 00:05:06.310 align:start position:0% which optimizes evm bytecode at this stage<00:05:03.620> has<00:05:03.889> no<00:05:04.100> idea<00:05:04.720> what<00:05:05.720> the<00:05:05.840> source<00:05:06.080> code 00:05:06.310 --> 00:05:06.320 align:start position:0% stage has no idea what the source code 00:05:06.320 --> 00:05:10.060 align:start position:0% stage has no idea what the source code was<00:05:07.930> now<00:05:08.930> introducing<00:05:09.500> an<00:05:09.620> intermediate 00:05:10.060 --> 00:05:10.070 align:start position:0% was now introducing an intermediate 00:05:10.070 --> 00:05:14.230 align:start position:0% was now introducing an intermediate language<00:05:10.220> we'll<00:05:10.610> change<00:05:10.940> it<00:05:11.180> to<00:05:11.540> or<00:05:12.470> till<00:05:13.240> all 00:05:14.230 --> 00:05:14.240 align:start position:0% language we'll change it to or till all 00:05:14.240 --> 00:05:17.110 align:start position:0% language we'll change it to or till all the<00:05:14.360> other<00:05:14.450> compilers<00:05:14.780> work<00:05:15.430> however<00:05:16.430> there 00:05:17.110 --> 00:05:17.120 align:start position:0% the other compilers work however there 00:05:17.120 --> 00:05:19.960 align:start position:0% the other compilers work however there is<00:05:17.330> a<00:05:17.360> big<00:05:17.930> difference<00:05:18.490> because<00:05:19.490> the<00:05:19.580> reason 00:05:19.960 --> 00:05:19.970 align:start position:0% is a big difference because the reason 00:05:19.970 --> 00:05:22.510 align:start position:0% is a big difference because the reason most<00:05:20.180> compilers<00:05:20.479> work<00:05:20.930> that<00:05:21.139> way<00:05:21.380> is<00:05:21.620> they 00:05:22.510 --> 00:05:22.520 align:start position:0% most compilers work that way is they 00:05:22.520 --> 00:05:25.029 align:start position:0% most compilers work that way is they target<00:05:22.940> multiple<00:05:23.090> machines<00:05:23.710> so<00:05:24.710> if<00:05:24.800> you<00:05:24.889> look 00:05:25.029 --> 00:05:25.039 align:start position:0% target multiple machines so if you look 00:05:25.039 --> 00:05:28.900 align:start position:0% target multiple machines so if you look at<00:05:25.130> GCC<00:05:25.610> or<00:05:25.850> LLVM<00:05:26.419> they<00:05:27.139> support<00:05:27.620> a<00:05:27.800> like<00:05:28.430> C<00:05:28.669> and 00:05:28.900 --> 00:05:28.910 align:start position:0% at GCC or LLVM they support a like C and 00:05:28.910 --> 00:05:31.510 align:start position:0% at GCC or LLVM they support a like C and you<00:05:29.720> can<00:05:29.870> compile<00:05:30.199> the<00:05:30.289> same<00:05:30.440> C<00:05:30.710> code<00:05:31.160> to 00:05:31.510 --> 00:05:31.520 align:start position:0% you can compile the same C code to 00:05:31.520 --> 00:05:34.840 align:start position:0% you can compile the same C code to multiple<00:05:31.970> computers<00:05:32.479> and<00:05:33.250> with<00:05:34.250> compiler 00:05:34.840 --> 00:05:34.850 align:start position:0% multiple computers and with compiler 00:05:34.850 --> 00:05:37.180 align:start position:0% multiple computers and with compiler toolkits<00:05:35.360> they<00:05:35.900> also<00:05:36.110> support<00:05:36.979> multiple 00:05:37.180 --> 00:05:37.190 align:start position:0% toolkits they also support multiple 00:05:37.190 --> 00:05:39.909 align:start position:0% toolkits they also support multiple languages<00:05:37.700> on<00:05:37.850> the<00:05:37.880> input<00:05:38.210> side<00:05:38.500> and<00:05:39.500> they<00:05:39.680> can 00:05:39.909 --> 00:05:39.919 align:start position:0% languages on the input side and they can 00:05:39.919 --> 00:05:42.670 align:start position:0% languages on the input side and they can utilize<00:05:40.340> the<00:05:40.550> same<00:05:40.580> back-end<00:05:41.240> written<00:05:41.680> of 00:05:42.670 --> 00:05:42.680 align:start position:0% utilize the same back-end written of 00:05:42.680 --> 00:05:45.190 align:start position:0% utilize the same back-end written of course<00:05:42.770> this<00:05:43.160> applies<00:05:43.490> to<00:05:43.520> solidity<00:05:44.120> but<00:05:45.080> the 00:05:45.190 --> 00:05:45.200 align:start position:0% course this applies to solidity but the 00:05:45.200 --> 00:05:47.589 align:start position:0% course this applies to solidity but the main<00:05:45.380> reason<00:05:45.970> this<00:05:46.970> makes<00:05:47.210> sense<00:05:47.389> for 00:05:47.589 --> 00:05:47.599 align:start position:0% main reason this makes sense for 00:05:47.599 --> 00:05:50.980 align:start position:0% main reason this makes sense for solidity<00:05:48.020> is<00:05:48.310> verification<00:05:49.310> of<00:05:49.940> what<00:05:50.570> happens 00:05:50.980 --> 00:05:50.990 align:start position:0% solidity is verification of what happens 00:05:50.990 --> 00:05:54.460 align:start position:0% solidity is verification of what happens within<00:05:51.229> the<00:05:51.320> compiler<00:05:53.050> well<00:05:54.050> actually<00:05:54.169> I<00:05:54.380> just 00:05:54.460 --> 00:05:54.470 align:start position:0% within the compiler well actually I just 00:05:54.470 --> 00:05:58.120 align:start position:0% within the compiler well actually I just said<00:05:54.770> these<00:05:54.950> there<00:05:55.340> and<00:05:56.349> yeah<00:05:57.349> like<00:05:57.620> the<00:05:57.770> last 00:05:58.120 --> 00:05:58.130 align:start position:0% said these there and yeah like the last 00:05:58.130 --> 00:06:01.180 align:start position:0% said these there and yeah like the last point<00:05:58.340> in<00:05:58.550> your<00:05:58.639> bytecode<00:05:59.210> and<00:05:59.979> since<00:06:00.979> this 00:06:01.180 --> 00:06:01.190 align:start position:0% point in your bytecode and since this 00:06:01.190 --> 00:06:02.860 align:start position:0% point in your bytecode and since this intermediate<00:06:01.789> representation<00:06:02.660> this 00:06:02.860 --> 00:06:02.870 align:start position:0% intermediate representation this 00:06:02.870 --> 00:06:06.129 align:start position:0% intermediate representation this language<00:06:03.310> by<00:06:04.310> definition<00:06:04.639> has<00:06:05.030> to<00:06:05.060> be<00:06:05.360> a<00:06:05.630> much 00:06:06.129 --> 00:06:06.139 align:start position:0% language by definition has to be a much 00:06:06.139 --> 00:06:08.560 align:start position:0% language by definition has to be a much simpler<00:06:06.620> language<00:06:06.800> than<00:06:07.610> solidity<00:06:08.060> is<00:06:08.300> and 00:06:08.560 --> 00:06:08.570 align:start position:0% simpler language than solidity is and 00:06:08.570 --> 00:06:10.510 align:start position:0% simpler language than solidity is and that<00:06:09.080> of<00:06:09.200> course<00:06:09.229> means<00:06:09.620> the<00:06:10.310> bytecode 00:06:10.510 --> 00:06:10.520 align:start position:0% that of course means the bytecode 00:06:10.520 --> 00:06:12.760 align:start position:0% that of course means the bytecode generation<00:06:11.270> of<00:06:11.479> it<00:06:11.720> should<00:06:12.200> be<00:06:12.349> much<00:06:12.560> more 00:06:12.760 --> 00:06:12.770 align:start position:0% generation of it should be much more 00:06:12.770 --> 00:06:16.420 align:start position:0% generation of it should be much more simple<00:06:13.010> so<00:06:14.650> what<00:06:15.650> does<00:06:15.800> the<00:06:15.889> language<00:06:16.039> look 00:06:16.420 --> 00:06:16.430 align:start position:0% simple so what does the language look 00:06:16.430 --> 00:06:20.500 align:start position:0% simple so what does the language look like<00:06:17.470> here's<00:06:18.470> a<00:06:18.560> simple<00:06:18.860> contract<00:06:19.270> it<00:06:20.270> just 00:06:20.500 --> 00:06:20.510 align:start position:0% like here's a simple contract it just 00:06:20.510 --> 00:06:23.860 align:start position:0% like here's a simple contract it just returns<00:06:20.810> a<00:06:21.139> string<00:06:21.340> and<00:06:22.360> this<00:06:23.360> is<00:06:23.630> an 00:06:23.860 --> 00:06:23.870 align:start position:0% returns a string and this is an 00:06:23.870 --> 00:06:26.740 align:start position:0% returns a string and this is an incomplete<00:06:24.139> example<00:06:24.860> of<00:06:25.039> that<00:06:26.000> contract<00:06:26.510> in 00:06:26.740 --> 00:06:26.750 align:start position:0% incomplete example of that contract in 00:06:26.750 --> 00:06:29.529 align:start position:0% incomplete example of that contract in julia<00:06:27.260> the<00:06:27.789> important<00:06:28.789> part<00:06:29.000> is<00:06:29.210> the<00:06:29.389> one 00:06:29.529 --> 00:06:29.539 align:start position:0% julia the important part is the one 00:06:29.539 --> 00:06:32.050 align:start position:0% julia the important part is the one highlighted<00:06:30.139> on<00:06:30.260> the<00:06:30.380> top<00:06:30.560> so<00:06:31.310> you<00:06:31.340> create<00:06:31.789> the 00:06:32.050 --> 00:06:32.060 align:start position:0% highlighted on the top so you create the 00:06:32.060 --> 00:06:35.469 align:start position:0% highlighted on the top so you create the if<00:06:33.050> you<00:06:33.169> look<00:06:33.260> at<00:06:33.380> the<00:06:33.470> string<00:06:33.970> that<00:06:34.970> string<00:06:35.300> is 00:06:35.469 --> 00:06:35.479 align:start position:0% if you look at the string that string is 00:06:35.479 --> 00:06:39.130 align:start position:0% if you look at the string that string is encoded<00:06:35.960> there<00:06:36.200> in<00:06:36.979> hexadecimal<00:06:37.960> it<00:06:38.960> is 00:06:39.130 --> 00:06:39.140 align:start position:0% encoded there in hexadecimal it is 00:06:39.140 --> 00:06:41.559 align:start position:0% encoded there in hexadecimal it is assigned<00:06:39.380> to<00:06:39.530> a<00:06:39.620> variable<00:06:39.770> it<00:06:40.250> is<00:06:40.640> ABI<00:06:41.060> encode 00:06:41.559 --> 00:06:41.569 align:start position:0% assigned to a variable it is ABI encode 00:06:41.569 --> 00:06:43.980 align:start position:0% assigned to a variable it is ABI encode into<00:06:41.869> memory<00:06:42.169> and<00:06:42.469> death<00:06:42.949> memories<00:06:43.339> return 00:06:43.980 --> 00:06:43.990 align:start position:0% into memory and death memories return 00:06:43.990 --> 00:06:46.809 align:start position:0% into memory and death memories return the<00:06:44.990> part<00:06:45.229> in<00:06:45.349> the<00:06:45.439> bottom<00:06:45.740> is<00:06:46.009> you<00:06:46.729> know 00:06:46.809 --> 00:06:46.819 align:start position:0% the part in the bottom is you know 00:06:46.819 --> 00:06:50.079 align:start position:0% the part in the bottom is you know helper<00:06:47.419> a<00:06:47.629> compiler<00:06:48.589> real<00:06:48.889> output<00:06:49.189> into<00:06:49.969> the 00:06:50.079 --> 00:06:50.089 align:start position:0% helper a compiler real output into the 00:06:50.089 --> 00:06:52.839 align:start position:0% helper a compiler real output into the contracts<00:06:50.569> what<00:06:51.169> it<00:06:51.289> helper<00:06:51.649> does<00:06:51.830> is<00:06:52.069> it 00:06:52.839 --> 00:06:52.849 align:start position:0% contracts what it helper does is it 00:06:52.849 --> 00:06:55.779 align:start position:0% contracts what it helper does is it receives<00:06:53.800> control<00:06:54.800> when<00:06:55.249> the<00:06:55.339> contract<00:06:55.699> is 00:06:55.779 --> 00:06:55.789 align:start position:0% receives control when the contract is 00:06:55.789 --> 00:06:58.089 align:start position:0% receives control when the contract is called<00:06:55.999> and<00:06:56.719> it<00:06:56.839> decides<00:06:57.229> which<00:06:57.469> function 00:06:58.089 --> 00:06:58.099 align:start position:0% called and it decides which function 00:06:58.099 --> 00:07:00.489 align:start position:0% called and it decides which function within<00:06:59.059> the<00:06:59.179> contract<00:06:59.629> should<00:06:59.779> be<00:06:59.839> executed 00:07:00.489 --> 00:07:00.499 align:start position:0% within the contract should be executed 00:07:00.499 --> 00:07:03.369 align:start position:0% within the contract should be executed or<00:07:00.849> in<00:07:01.849> the<00:07:01.939> case<00:07:02.149> none<00:07:02.330> of<00:07:02.360> the<00:07:02.449> match<00:07:02.779> it<00:07:03.199> just 00:07:03.369 --> 00:07:03.379 align:start position:0% or in the case none of the match it just 00:07:03.379 --> 00:07:04.929 align:start position:0% or in the case none of the match it just ensures<00:07:03.529> that<00:07:03.740> the<00:07:04.189> contract<00:07:04.610> hasn't 00:07:04.929 --> 00:07:04.939 align:start position:0% ensures that the contract hasn't 00:07:04.939 --> 00:07:09.100 align:start position:0% ensures that the contract hasn't received<00:07:05.300> any<00:07:05.599> money<00:07:06.939> and<00:07:07.939> you<00:07:08.629> can<00:07:08.749> extend 00:07:09.100 --> 00:07:09.110 align:start position:0% received any money and you can extend 00:07:09.110 --> 00:07:11.379 align:start position:0% received any money and you can extend this<00:07:09.349> with<00:07:09.860> the<00:07:09.979> missing<00:07:10.249> parts<00:07:10.580> because<00:07:11.240> you 00:07:11.379 --> 00:07:11.389 align:start position:0% this with the missing parts because you 00:07:11.389 --> 00:07:14.279 align:start position:0% this with the missing parts because you see<00:07:11.629> there's<00:07:12.439> an<00:07:12.529> ABI<00:07:12.919> in<00:07:13.279> code<00:07:13.520> string<00:07:13.939> and 00:07:14.279 --> 00:07:14.289 align:start position:0% see there's an ABI in code string and 00:07:14.289 --> 00:07:17.769 align:start position:0% see there's an ABI in code string and sure<00:07:15.289> nowhere<00:07:15.860> you<00:07:16.009> transfer<00:07:16.629> extract<00:07:17.629> code 00:07:17.769 --> 00:07:17.779 align:start position:0% sure nowhere you transfer extract code 00:07:17.779 --> 00:07:21.609 align:start position:0% sure nowhere you transfer extract code signature<00:07:18.080> so<00:07:18.919> these<00:07:19.039> are<00:07:19.279> in<00:07:19.999> this<00:07:20.149> slide<00:07:20.619> of 00:07:21.609 --> 00:07:21.619 align:start position:0% signature so these are in this slide of 00:07:21.619 --> 00:07:23.230 align:start position:0% signature so these are in this slide of course<00:07:21.919> not<00:07:22.339> all<00:07:22.369> of<00:07:22.550> them<00:07:22.669> are<00:07:22.729> implemented 00:07:23.230 --> 00:07:23.240 align:start position:0% course not all of them are implemented 00:07:23.240 --> 00:07:25.299 align:start position:0% course not all of them are implemented and<00:07:23.529> but<00:07:24.529> you<00:07:24.589> can<00:07:24.740> see<00:07:24.860> they<00:07:25.009> are<00:07:25.039> fairly 00:07:25.299 --> 00:07:25.309 align:start position:0% and but you can see they are fairly 00:07:25.309 --> 00:07:28.059 align:start position:0% and but you can see they are fairly simple<00:07:25.669> these<00:07:26.149> are<00:07:26.180> all<00:07:26.449> helpers<00:07:26.990> which<00:07:27.830> will 00:07:28.059 --> 00:07:28.069 align:start position:0% simple these are all helpers which will 00:07:28.069 --> 00:07:30.790 align:start position:0% simple these are all helpers which will be<00:07:28.249> I<00:07:28.459> put<00:07:28.789> it<00:07:28.939> into<00:07:29.509> each<00:07:30.139> of<00:07:30.319> the<00:07:30.409> contracts 00:07:30.790 --> 00:07:30.800 align:start position:0% be I put it into each of the contracts 00:07:30.800 --> 00:07:32.679 align:start position:0% be I put it into each of the contracts and<00:07:30.889> that<00:07:31.069> happens<00:07:31.459> already<00:07:31.759> but<00:07:32.330> all<00:07:32.449> of<00:07:32.569> this 00:07:32.679 --> 00:07:32.689 align:start position:0% and that happens already but all of this 00:07:32.689 --> 00:07:35.139 align:start position:0% and that happens already but all of this is<00:07:32.749> written<00:07:33.110> in<00:07:33.289> C++<00:07:33.830> and<00:07:34.009> is<00:07:34.490> hidden<00:07:34.789> from<00:07:34.969> the 00:07:35.139 --> 00:07:35.149 align:start position:0% is written in C++ and is hidden from the 00:07:35.149 --> 00:07:39.129 align:start position:0% is written in C++ and is hidden from the eye<00:07:36.099> there<00:07:37.099> is<00:07:37.189> one<00:07:37.430> thing<00:07:37.729> which<00:07:37.999> one<00:07:38.809> can 00:07:39.129 --> 00:07:39.139 align:start position:0% eye there is one thing which one can 00:07:39.139 --> 00:07:42.609 align:start position:0% eye there is one thing which one can notice<00:07:39.919> here<00:07:40.539> extra<00:07:41.539> code<00:07:41.719> signature<00:07:42.080> is<00:07:42.409> a 00:07:42.609 --> 00:07:42.619 align:start position:0% notice here extra code signature is a 00:07:42.619 --> 00:07:45.579 align:start position:0% notice here extra code signature is a one-liner<00:07:43.419> that's<00:07:44.419> why<00:07:44.629> optimizations<00:07:45.349> make 00:07:45.579 --> 00:07:45.589 align:start position:0% one-liner that's why optimizations make 00:07:45.589 --> 00:07:48.549 align:start position:0% one-liner that's why optimizations make sense<00:07:45.919> this<00:07:46.759> one<00:07:47.029> should<00:07:47.330> be<00:07:47.360> inlined<00:07:47.930> it 00:07:48.549 --> 00:07:48.559 align:start position:0% sense this one should be inlined it 00:07:48.559 --> 00:07:50.379 align:start position:0% sense this one should be inlined it shouldn't<00:07:48.919> be<00:07:49.009> a<00:07:49.039> function<00:07:49.430> call<00:07:49.669> it<00:07:50.149> should 00:07:50.379 --> 00:07:50.389 align:start position:0% shouldn't be a function call it should 00:07:50.389 --> 00:07:55.719 align:start position:0% shouldn't be a function call it should be<00:07:50.509> just<00:07:50.860> those<00:07:51.860> few<00:07:52.279> instructions<00:07:54.729> now 00:07:55.719 --> 00:07:55.729 align:start position:0% be just those few instructions now 00:07:55.729 --> 00:07:58.589 align:start position:0% be just those few instructions now here's<00:07:56.119> the<00:07:56.330> the<00:07:56.599> helper<00:07:56.959> you<00:07:57.649> have<00:07:57.740> seen<00:07:57.979> and 00:07:58.589 --> 00:07:58.599 align:start position:0% here's the the helper you have seen and 00:07:58.599 --> 00:08:00.790 align:start position:0% here's the the helper you have seen and here's<00:07:59.599> a<00:07:59.659> possible<00:07:59.990> way<00:08:00.139> to<00:08:00.199> write<00:08:00.529> it<00:08:00.559> in 00:08:00.790 --> 00:08:00.800 align:start position:0% here's a possible way to write it in 00:08:00.800 --> 00:08:06.100 align:start position:0% here's a possible way to write it in julia<00:08:01.159> i<00:08:01.399> think<00:08:01.999> it's<00:08:02.089> much<00:08:02.209> more<00:08:02.269> readable<00:08:05.110> so 00:08:06.100 --> 00:08:06.110 align:start position:0% julia i think it's much more readable so 00:08:06.110 --> 00:08:08.079 align:start position:0% julia i think it's much more readable so you<00:08:06.740> know<00:08:06.860> by<00:08:07.009> moving<00:08:07.279> most<00:08:07.550> of<00:08:07.669> the<00:08:07.729> compiler 00:08:08.079 --> 00:08:08.089 align:start position:0% you know by moving most of the compiler 00:08:08.089 --> 00:08:10.899 align:start position:0% you know by moving most of the compiler into<00:08:08.360> julia<00:08:08.749> from<00:08:08.990> C++<00:08:09.369> gives<00:08:10.369> us<00:08:10.519> a<00:08:10.579> couple<00:08:10.819> of 00:08:10.899 --> 00:08:10.909 align:start position:0% into julia from C++ gives us a couple of 00:08:10.909 --> 00:08:13.230 align:start position:0% into julia from C++ gives us a couple of benefits<00:08:11.059> it<00:08:11.899> should<00:08:12.110> help<00:08:12.289> auditing<00:08:12.740> efforts 00:08:13.230 --> 00:08:13.240 align:start position:0% benefits it should help auditing efforts 00:08:13.240 --> 00:08:16.029 align:start position:0% benefits it should help auditing efforts because<00:08:14.240> one<00:08:14.749> can't<00:08:15.019> just<00:08:15.079> review<00:08:15.589> this<00:08:15.829> much 00:08:16.029 --> 00:08:16.039 align:start position:0% because one can't just review this much 00:08:16.039 --> 00:08:18.249 align:start position:0% because one can't just review this much more<00:08:16.219> simple<00:08:16.519> language<00:08:16.669> Julia<00:08:17.329> and<00:08:17.629> all<00:08:18.169> the 00:08:18.249 --> 00:08:18.259 align:start position:0% more simple language Julia and all the 00:08:18.259 --> 00:08:21.089 align:start position:0% more simple language Julia and all the helpers<00:08:18.619> written<00:08:19.099> in<00:08:19.189> them<00:08:19.339> as<00:08:19.899> opposed<00:08:20.899> to 00:08:21.089 --> 00:08:21.099 align:start position:0% helpers written in them as opposed to 00:08:21.099 --> 00:08:24.040 align:start position:0% helpers written in them as opposed to finding<00:08:22.099> someone<00:08:22.459> who<00:08:23.119> is<00:08:23.180> happy<00:08:23.509> to<00:08:23.659> review 00:08:24.040 --> 00:08:24.050 align:start position:0% finding someone who is happy to review 00:08:24.050 --> 00:08:29.159 align:start position:0% finding someone who is happy to review C++<00:08:24.740> I<00:08:25.009> mean<00:08:25.909> I<00:08:25.939> wouldn't<00:08:26.329> want<00:08:26.509> to<00:08:26.539> review<00:08:26.839> C++ 00:08:29.159 --> 00:08:29.169 align:start position:0% C++ I mean I wouldn't want to review C++ 00:08:29.169 --> 00:08:32.469 align:start position:0% C++ I mean I wouldn't want to review C++ and<00:08:30.169> it<00:08:30.680> also<00:08:30.829> allows<00:08:31.249> a<00:08:31.639> simple<00:08:32.209> framework 00:08:32.469 --> 00:08:32.479 align:start position:0% and it also allows a simple framework 00:08:32.479 --> 00:08:35.110 align:start position:0% and it also allows a simple framework for<00:08:32.810> optimizations<00:08:33.439> because<00:08:34.250> basically<00:08:34.459> here 00:08:35.110 --> 00:08:35.120 align:start position:0% for optimizations because basically here 00:08:35.120 --> 00:08:38.409 align:start position:0% for optimizations because basically here you<00:08:35.149> will<00:08:35.509> just<00:08:35.889> optimize<00:08:36.889> julia<00:08:37.610> code<00:08:37.880> right 00:08:38.409 --> 00:08:38.419 align:start position:0% you will just optimize julia code right 00:08:38.419 --> 00:08:39.879 align:start position:0% you will just optimize julia code right now<00:08:38.449> if<00:08:38.779> you<00:08:38.899> want<00:08:39.050> to<00:08:39.110> optimize<00:08:39.259> contracts 00:08:39.879 --> 00:08:39.889 align:start position:0% now if you want to optimize contracts 00:08:39.889 --> 00:08:42.249 align:start position:0% now if you want to optimize contracts you<00:08:40.399> should<00:08:40.610> also<00:08:40.789> do<00:08:41.060> optimization<00:08:41.719> steps<00:08:41.990> in 00:08:42.249 --> 00:08:42.259 align:start position:0% you should also do optimization steps in 00:08:42.259 --> 00:08:45.639 align:start position:0% you should also do optimization steps in solidity<00:08:43.069> in<00:08:43.579> the<00:08:43.669> solid<00:08:43.909> part<00:08:44.329> before<00:08:44.779> it 00:08:45.639 --> 00:08:45.649 align:start position:0% solidity in the solid part before it 00:08:45.649 --> 00:08:48.280 align:start position:0% solidity in the solid part before it gets<00:08:45.829> converted<00:08:46.100> to<00:08:46.310> EVM<00:08:46.699> and<00:08:46.970> in<00:08:47.750> fact<00:08:48.139> we 00:08:48.280 --> 00:08:48.290 align:start position:0% gets converted to EVM and in fact we 00:08:48.290 --> 00:08:51.610 align:start position:0% gets converted to EVM and in fact we only<00:08:48.319> have<00:08:48.649> one<00:08:48.920> single<00:08:49.610> tiny<00:08:50.620> simple 00:08:51.610 --> 00:08:51.620 align:start position:0% only have one single tiny simple 00:08:51.620 --> 00:08:53.980 align:start position:0% only have one single tiny simple optimization<00:08:52.370> step<00:08:52.610> in<00:08:52.790> solidity<00:08:53.209> everything 00:08:53.980 --> 00:08:53.990 align:start position:0% optimization step in solidity everything 00:08:53.990 --> 00:08:56.260 align:start position:0% optimization step in solidity everything else<00:08:54.170> is<00:08:54.380> in 00:08:56.260 --> 00:08:56.270 align:start position:0% else is in 00:08:56.270 --> 00:08:58.820 align:start position:0% else is in and<00:08:57.270> you<00:08:57.570> know<00:08:57.690> if<00:08:57.960> we<00:08:58.500> have<00:08:58.620> all<00:08:58.680> these 00:08:58.820 --> 00:08:58.830 align:start position:0% and you know if we have all these 00:08:58.830 --> 00:09:01.040 align:start position:0% and you know if we have all these helpers<00:08:59.160> written<00:08:59.460> in<00:08:59.550> Julia<00:08:59.850> and<00:09:00.150> they<00:09:00.930> are 00:09:01.040 --> 00:09:01.050 align:start position:0% helpers written in Julia and they are 00:09:01.050 --> 00:09:02.810 align:start position:0% helpers written in Julia and they are verified<00:09:01.410> they<00:09:02.100> could<00:09:02.280> be<00:09:02.400> used<00:09:02.610> by<00:09:02.790> other 00:09:02.810 --> 00:09:02.820 align:start position:0% verified they could be used by other 00:09:02.820 --> 00:09:06.110 align:start position:0% verified they could be used by other languages<00:09:03.300> as<00:09:03.540> well<00:09:03.750> in<00:09:03.990> the<00:09:04.410> ecosystem<00:09:05.120> so 00:09:06.110 --> 00:09:06.120 align:start position:0% languages as well in the ecosystem so 00:09:06.120 --> 00:09:10.790 align:start position:0% languages as well in the ecosystem so where<00:09:06.750> do<00:09:06.870> we<00:09:06.900> stand<00:09:07.260> right<00:09:07.440> now<00:09:09.590> Julia<00:09:10.590> I 00:09:10.790 --> 00:09:10.800 align:start position:0% where do we stand right now Julia I 00:09:10.800 --> 00:09:13.070 align:start position:0% where do we stand right now Julia I guess<00:09:11.070> looked<00:09:11.370> familiar<00:09:11.580> to<00:09:11.970> those<00:09:12.120> who<00:09:12.480> use 00:09:13.070 --> 00:09:13.080 align:start position:0% guess looked familiar to those who use 00:09:13.080 --> 00:09:14.990 align:start position:0% guess looked familiar to those who use solidity<00:09:13.560> because<00:09:14.250> it<00:09:14.370> looked<00:09:14.610> kind<00:09:14.880> of<00:09:14.940> like 00:09:14.990 --> 00:09:15.000 align:start position:0% solidity because it looked kind of like 00:09:15.000 --> 00:09:17.560 align:start position:0% solidity because it looked kind of like the<00:09:15.180> inline<00:09:15.450> assembly<00:09:15.930> solidity<00:09:16.740> has<00:09:17.010> and 00:09:17.560 --> 00:09:17.570 align:start position:0% the inline assembly solidity has and 00:09:17.570 --> 00:09:20.570 align:start position:0% the inline assembly solidity has and that's<00:09:18.570> of<00:09:18.690> course<00:09:18.720> because<00:09:19.020> it<00:09:19.380> is<00:09:19.580> an 00:09:20.570 --> 00:09:20.580 align:start position:0% that's of course because it is an 00:09:20.580 --> 00:09:23.810 align:start position:0% that's of course because it is an evolutionary<00:09:21.120> step<00:09:21.480> from<00:09:21.840> align<00:09:22.410> assembly<00:09:22.830> so 00:09:23.810 --> 00:09:23.820 align:start position:0% evolutionary step from align assembly so 00:09:23.820 --> 00:09:24.980 align:start position:0% evolutionary step from align assembly so you<00:09:23.910> know<00:09:24.000> somebody<00:09:24.330> was<00:09:24.480> introduced<00:09:24.840> last 00:09:24.980 --> 00:09:24.990 align:start position:0% you know somebody was introduced last 00:09:24.990 --> 00:09:28.010 align:start position:0% you know somebody was introduced last year<00:09:25.310> it's<00:09:26.310> supported<00:09:26.820> jumps<00:09:27.150> instructions 00:09:28.010 --> 00:09:28.020 align:start position:0% year it's supported jumps instructions 00:09:28.020 --> 00:09:31.100 align:start position:0% year it's supported jumps instructions and<00:09:28.230> functional<00:09:28.650> instructions<00:09:29.600> but<00:09:30.600> over 00:09:31.100 --> 00:09:31.110 align:start position:0% and functional instructions but over 00:09:31.110 --> 00:09:33.830 align:start position:0% and functional instructions but over time<00:09:31.350> we<00:09:31.590> have<00:09:31.710> restricted<00:09:32.310> that<00:09:32.450> we<00:09:33.450> remove 00:09:33.830 --> 00:09:33.840 align:start position:0% time we have restricted that we remove 00:09:33.840 --> 00:09:37.940 align:start position:0% time we have restricted that we remove the<00:09:34.940> you<00:09:35.940> know<00:09:36.060> more<00:09:36.240> risky<00:09:36.750> part<00:09:36.900> and<00:09:37.230> we 00:09:37.940 --> 00:09:37.950 align:start position:0% the you know more risky part and we 00:09:37.950 --> 00:09:39.230 align:start position:0% the you know more risky part and we added<00:09:38.130> a<00:09:38.280> couple<00:09:38.460> of<00:09:38.580> new<00:09:38.640> features<00:09:38.970> like 00:09:39.230 --> 00:09:39.240 align:start position:0% added a couple of new features like 00:09:39.240 --> 00:09:44.650 align:start position:0% added a couple of new features like functions<00:09:39.900> for<00:09:40.380> loops<00:09:40.590> which<00:09:41.070> statements<00:09:42.950> and 00:09:44.650 --> 00:09:44.660 align:start position:0% functions for loops which statements and 00:09:44.660 --> 00:09:48.620 align:start position:0% functions for loops which statements and yeah<00:09:46.190> okay<00:09:47.190> so<00:09:47.250> one<00:09:47.820> question<00:09:48.210> there 00:09:48.620 --> 00:09:48.630 align:start position:0% yeah okay so one question there 00:09:48.630 --> 00:09:51.950 align:start position:0% yeah okay so one question there I<00:09:48.660> guess<00:09:49.650> those<00:09:49.800> people<00:09:50.130> doing<00:09:50.900> serpent<00:09:51.900> the 00:09:51.950 --> 00:09:51.960 align:start position:0% I guess those people doing serpent the 00:09:51.960 --> 00:09:54.470 align:start position:0% I guess those people doing serpent the Viper<00:09:52.140> would<00:09:52.440> ask<00:09:52.620> why<00:09:53.370> not<00:09:53.640> do<00:09:53.850> it<00:09:53.880> with<00:09:54.030> LLL 00:09:54.470 --> 00:09:54.480 align:start position:0% Viper would ask why not do it with LLL 00:09:54.480 --> 00:09:57.320 align:start position:0% Viper would ask why not do it with LLL use<00:09:54.900> lll<00:09:55.230> axis<00:09:55.590> and<00:09:55.940> serpent<00:09:56.940> actually<00:09:57.210> use 00:09:57.320 --> 00:09:57.330 align:start position:0% use lll axis and serpent actually use 00:09:57.330 --> 00:10:00.830 align:start position:0% use lll axis and serpent actually use LLL<00:09:57.750> as<00:09:57.960> an<00:09:58.140> intermediate<00:09:58.590> language<00:09:59.000> so<00:10:00.000> the 00:10:00.830 --> 00:10:00.840 align:start position:0% LLL as an intermediate language so the 00:10:00.840 --> 00:10:03.350 align:start position:0% LLL as an intermediate language so the two<00:10:01.020> main<00:10:01.170> reasons<00:10:01.350> is<00:10:01.740> ll<00:10:02.430> L<00:10:02.580> is<00:10:02.790> really<00:10:03.060> based 00:10:03.350 --> 00:10:03.360 align:start position:0% two main reasons is ll L is really based 00:10:03.360 --> 00:10:05.630 align:start position:0% two main reasons is ll L is really based on<00:10:03.510> a<00:10:03.630> VM<00:10:03.900> it's<00:10:04.440> based<00:10:04.680> on<00:10:04.770> the<00:10:04.890> VM<00:10:05.160> opcodes 00:10:05.630 --> 00:10:05.640 align:start position:0% on a VM it's based on the VM opcodes 00:10:05.640 --> 00:10:07.850 align:start position:0% on a VM it's based on the VM opcodes it<00:10:06.060> has<00:10:06.180> a<00:10:06.210> couple<00:10:06.390> of<00:10:06.540> extensions<00:10:06.870> on<00:10:07.140> top<00:10:07.320> but 00:10:07.850 --> 00:10:07.860 align:start position:0% it has a couple of extensions on top but 00:10:07.860 --> 00:10:10.610 align:start position:0% it has a couple of extensions on top but it<00:10:07.950> really<00:10:08.160> is<00:10:08.400> just<00:10:08.430> a<00:10:09.420> VM<00:10:09.930> assembly<00:10:10.380> in<00:10:10.560> a 00:10:10.610 --> 00:10:10.620 align:start position:0% it really is just a VM assembly in a 00:10:10.620 --> 00:10:13.910 align:start position:0% it really is just a VM assembly in a lisp<00:10:11.070> like<00:10:11.340> language<00:10:11.760> and<00:10:12.470> of<00:10:13.470> course<00:10:13.680> we<00:10:13.800> have 00:10:13.910 --> 00:10:13.920 align:start position:0% lisp like language and of course we have 00:10:13.920 --> 00:10:15.650 align:start position:0% lisp like language and of course we have this<00:10:14.040> organic<00:10:14.400> evolution<00:10:14.640> of<00:10:15.210> inline 00:10:15.650 --> 00:10:15.660 align:start position:0% this organic evolution of inline 00:10:15.660 --> 00:10:19.760 align:start position:0% this organic evolution of inline assembly<00:10:16.080> which<00:10:16.620> was<00:10:16.650> already<00:10:16.890> used<00:10:18.200> so<00:10:19.200> the 00:10:19.760 --> 00:10:19.770 align:start position:0% assembly which was already used so the 00:10:19.770 --> 00:10:22.190 align:start position:0% assembly which was already used so the language<00:10:19.920> features<00:10:20.220> we<00:10:20.610> have<00:10:21.020> we<00:10:22.020> have 00:10:22.190 --> 00:10:22.200 align:start position:0% language features we have we have 00:10:22.200 --> 00:10:25.430 align:start position:0% language features we have we have variables<00:10:22.620> which<00:10:23.400> can<00:10:23.550> be<00:10:23.700> typed<00:10:24.230> well<00:10:25.230> in 00:10:25.430 --> 00:10:25.440 align:start position:0% variables which can be typed well in 00:10:25.440 --> 00:10:27.980 align:start position:0% variables which can be typed well in fact<00:10:25.880> there's<00:10:26.880> Julia<00:10:27.240> which<00:10:27.750> is<00:10:27.900> the 00:10:27.980 --> 00:10:27.990 align:start position:0% fact there's Julia which is the 00:10:27.990 --> 00:10:30.200 align:start position:0% fact there's Julia which is the intermediate<00:10:28.380> language<00:10:28.580> that<00:10:29.580> must<00:10:29.760> be<00:10:29.850> typed 00:10:30.200 --> 00:10:30.210 align:start position:0% intermediate language that must be typed 00:10:30.210 --> 00:10:33.140 align:start position:0% intermediate language that must be typed and<00:10:31.080> then<00:10:31.380> we<00:10:31.530> have<00:10:31.620> inline<00:10:31.890> assembly<00:10:32.310> which 00:10:33.140 --> 00:10:33.150 align:start position:0% and then we have inline assembly which 00:10:33.150 --> 00:10:36.220 align:start position:0% and then we have inline assembly which you<00:10:33.330> can<00:10:33.450> already<00:10:33.630> use<00:10:33.890> that<00:10:34.890> is<00:10:35.040> not<00:10:35.190> typed 00:10:36.220 --> 00:10:36.230 align:start position:0% you can already use that is not typed 00:10:36.230 --> 00:10:38.510 align:start position:0% you can already use that is not typed the<00:10:37.230> a<00:10:37.260> function<00:10:37.470> switch<00:10:37.950> statement 00:10:38.510 --> 00:10:38.520 align:start position:0% the a function switch statement 00:10:38.520 --> 00:10:41.540 align:start position:0% the a function switch statement I<00:10:39.680> guess<00:10:40.680> soon<00:10:40.860> we<00:10:41.040> will<00:10:41.190> have<00:10:41.340> an<00:10:41.430> if 00:10:41.540 --> 00:10:41.550 align:start position:0% I guess soon we will have an if 00:10:41.550 --> 00:10:43.460 align:start position:0% I guess soon we will have an if statement<00:10:41.730> as<00:10:42.120> well<00:10:42.300> video<00:10:42.870> today<00:10:43.200> else 00:10:43.460 --> 00:10:43.470 align:start position:0% statement as well video today else 00:10:43.470 --> 00:10:46.940 align:start position:0% statement as well video today else condition<00:10:44.340> and<00:10:44.660> via<00:10:45.660> for<00:10:45.900> loops<00:10:46.110> then 00:10:46.940 --> 00:10:46.950 align:start position:0% condition and via for loops then 00:10:46.950 --> 00:10:48.740 align:start position:0% condition and via for loops then important<00:10:47.430> part<00:10:47.700> we<00:10:48.390> don't<00:10:48.570> have 00:10:48.740 --> 00:10:48.750 align:start position:0% important part we don't have 00:10:48.750 --> 00:10:52.730 align:start position:0% important part we don't have instructions<00:10:49.940> evm<00:10:50.940> op<00:10:51.090> codes<00:10:51.470> behave<00:10:52.470> just 00:10:52.730 --> 00:10:52.740 align:start position:0% instructions evm op codes behave just 00:10:52.740 --> 00:10:54.680 align:start position:0% instructions evm op codes behave just like<00:10:52.800> functions<00:10:53.370> they<00:10:53.550> are<00:10:53.580> not<00:10:53.730> a<00:10:54.000> separate 00:10:54.680 --> 00:10:54.690 align:start position:0% like functions they are not a separate 00:10:54.690 --> 00:11:00.290 align:start position:0% like functions they are not a separate kind<00:10:55.110> of<00:10:55.970> expression<00:10:58.070> so<00:10:59.150> variables<00:11:00.150> and 00:11:00.290 --> 00:11:00.300 align:start position:0% kind of expression so variables and 00:11:00.300 --> 00:11:02.480 align:start position:0% kind of expression so variables and functions<00:11:00.480> this<00:11:01.410> support<00:11:02.220> multiple 00:11:02.480 --> 00:11:02.490 align:start position:0% functions this support multiple 00:11:02.490 --> 00:11:04.280 align:start position:0% functions this support multiple assignment<00:11:03.060> the<00:11:03.510> earliest<00:11:03.750> relies<00:11:04.050> to<00:11:04.170> the 00:11:04.280 --> 00:11:04.290 align:start position:0% assignment the earliest relies to the 00:11:04.290 --> 00:11:07.520 align:start position:0% assignment the earliest relies to the default<00:11:04.770> value<00:11:05.460> of<00:11:05.520> 0<00:11:05.910> and<00:11:06.320> functions<00:11:07.320> can 00:11:07.520 --> 00:11:07.530 align:start position:0% default value of 0 and functions can 00:11:07.530 --> 00:11:09.170 align:start position:0% default value of 0 and functions can have<00:11:07.560> multiple<00:11:08.040> inputs<00:11:08.190> and<00:11:08.550> multiplied 00:11:09.170 --> 00:11:09.180 align:start position:0% have multiple inputs and multiplied 00:11:09.180 --> 00:11:11.990 align:start position:0% have multiple inputs and multiplied so<00:11:10.170> here<00:11:10.470> here<00:11:10.800> are<00:11:10.860> a<00:11:10.890> couple<00:11:10.920> of<00:11:11.160> examples<00:11:11.280> on 00:11:11.990 --> 00:11:12.000 align:start position:0% so here here are a couple of examples on 00:11:12.000 --> 00:11:14.360 align:start position:0% so here here are a couple of examples on a<00:11:12.110> table<00:11:13.110> you<00:11:13.140> just<00:11:13.380> have<00:11:13.650> a<00:11:13.680> same<00:11:13.920> simple 00:11:14.360 --> 00:11:14.370 align:start position:0% a table you just have a same simple 00:11:14.370 --> 00:11:16.940 align:start position:0% a table you just have a same simple excitement<00:11:14.940> if<00:11:15.810> there's<00:11:16.440> no<00:11:16.590> where<00:11:16.830> you 00:11:16.940 --> 00:11:16.950 align:start position:0% excitement if there's no where you 00:11:16.950 --> 00:11:20.950 align:start position:0% excitement if there's no where you specify<00:11:17.190> it<00:11:17.520> as<00:11:17.730> assigned<00:11:18.120> a<00:11:18.480> zero<00:11:19.190> oh 00:11:20.950 --> 00:11:20.960 align:start position:0% specify it as assigned a zero oh 00:11:20.960 --> 00:11:25.130 align:start position:0% specify it as assigned a zero oh actually<00:11:21.960> the<00:11:22.860> third<00:11:23.010> line<00:11:23.280> is<00:11:23.900> invalid 00:11:25.130 --> 00:11:25.140 align:start position:0% actually the third line is invalid 00:11:25.140 --> 00:11:29.270 align:start position:0% actually the third line is invalid I<00:11:25.190> just<00:11:26.190> miss<00:11:27.030> to<00:11:27.240> market<00:11:27.890> because<00:11:28.890> right<00:11:29.100> hand 00:11:29.270 --> 00:11:29.280 align:start position:0% I just miss to market because right hand 00:11:29.280 --> 00:11:31.550 align:start position:0% I just miss to market because right hand side<00:11:29.520> has<00:11:30.000> to<00:11:30.030> be<00:11:30.240> a<00:11:30.510> single<00:11:30.960> expression<00:11:31.230> it 00:11:31.550 --> 00:11:31.560 align:start position:0% side has to be a single expression it 00:11:31.560 --> 00:11:34.310 align:start position:0% side has to be a single expression it cannot<00:11:31.770> be<00:11:31.950> a<00:11:31.980> tuple<00:11:32.280> expression<00:11:32.900> and<00:11:33.900> that<00:11:34.110> is 00:11:34.310 --> 00:11:34.320 align:start position:0% cannot be a tuple expression and that is 00:11:34.320 --> 00:11:35.570 align:start position:0% cannot be a tuple expression and that is a<00:11:34.350> simple<00:11:34.710> function<00:11:34.890> and<00:11:35.250> that's<00:11:35.400> how<00:11:35.520> you 00:11:35.570 --> 00:11:35.580 align:start position:0% a simple function and that's how you 00:11:35.580 --> 00:11:40.130 align:start position:0% a simple function and that's how you call<00:11:35.820> it<00:11:36.740> now<00:11:37.740> the<00:11:38.190> switch<00:11:38.430> statement<00:11:38.550> is<00:11:39.140> the 00:11:40.130 --> 00:11:40.140 align:start position:0% call it now the switch statement is the 00:11:40.140 --> 00:11:44.600 align:start position:0% call it now the switch statement is the core<00:11:40.440> of<00:11:41.240> the<00:11:42.240> entire<00:11:42.450> language<00:11:43.070> it<00:11:44.070> can<00:11:44.430> have 00:11:44.600 --> 00:11:44.610 align:start position:0% core of the entire language it can have 00:11:44.610 --> 00:11:45.950 align:start position:0% core of the entire language it can have multiple<00:11:44.940> cases<00:11:45.060> it<00:11:45.450> can<00:11:45.570> have<00:11:45.720> a<00:11:45.780> default 00:11:45.950 --> 00:11:45.960 align:start position:0% multiple cases it can have a default 00:11:45.960 --> 00:11:51.380 align:start position:0% multiple cases it can have a default value<00:11:46.550> at<00:11:47.550> least<00:11:48.210> one<00:11:48.540> case<00:11:48.830> either<00:11:50.390> specified 00:11:51.380 --> 00:11:51.390 align:start position:0% value at least one case either specified 00:11:51.390 --> 00:11:52.820 align:start position:0% value at least one case either specified case<00:11:51.570> or<00:11:51.720> the<00:11:51.810> default<00:11:52.080> case<00:11:52.230> has<00:11:52.620> to<00:11:52.740> be 00:11:52.820 --> 00:11:52.830 align:start position:0% case or the default case has to be 00:11:52.830 --> 00:11:56.180 align:start position:0% case or the default case has to be present<00:11:53.270> one<00:11:54.270> major<00:11:54.510> difference<00:11:54.780> here<00:11:55.190> for 00:11:56.180 --> 00:11:56.190 align:start position:0% present one major difference here for 00:11:56.190 --> 00:11:59.900 align:start position:0% present one major difference here for anyone<00:11:57.140> used<00:11:58.140> to<00:11:58.350> normal<00:11:58.800> languages<00:11:59.220> is<00:11:59.400> a 00:11:59.900 --> 00:11:59.910 align:start position:0% anyone used to normal languages is a 00:11:59.910 --> 00:12:01.910 align:start position:0% anyone used to normal languages is a switch<00:12:00.180> statement<00:12:00.300> with<00:12:00.840> support<00:12:01.350> for<00:12:01.620> true 00:12:01.910 --> 00:12:01.920 align:start position:0% switch statement with support for true 00:12:01.920 --> 00:12:04.430 align:start position:0% switch statement with support for true and<00:12:02.130> you<00:12:02.640> would<00:12:02.760> have<00:12:02.820> a<00:12:02.910> keyboard<00:12:03.210> break<00:12:03.540> to 00:12:04.430 --> 00:12:04.440 align:start position:0% and you would have a keyboard break to 00:12:04.440 --> 00:12:05.990 align:start position:0% and you would have a keyboard break to stop<00:12:04.620> at<00:12:04.740> any<00:12:04.830> given<00:12:05.100> point<00:12:05.280> of<00:12:05.460> time 00:12:05.990 --> 00:12:06.000 align:start position:0% stop at any given point of time 00:12:06.000 --> 00:12:08.650 align:start position:0% stop at any given point of time naturally<00:12:06.930> it<00:12:07.020> doesn't<00:12:07.230> have<00:12:07.380> that<00:12:07.590> every 00:12:08.650 --> 00:12:08.660 align:start position:0% naturally it doesn't have that every 00:12:08.660 --> 00:12:12.980 align:start position:0% naturally it doesn't have that every part<00:12:09.660> of<00:12:09.870> a<00:12:10.020> switch<00:12:10.260> statement<00:12:11.960> will<00:12:12.960> be 00:12:12.980 --> 00:12:12.990 align:start position:0% part of a switch statement will be 00:12:12.990 --> 00:12:15.440 align:start position:0% part of a switch statement will be executed<00:12:13.440> entirely<00:12:14.400> there's<00:12:14.700> no<00:12:14.880> break<00:12:15.120> and 00:12:15.440 --> 00:12:15.450 align:start position:0% executed entirely there's no break and 00:12:15.450 --> 00:12:18.020 align:start position:0% executed entirely there's no break and there's<00:12:16.020> no<00:12:16.200> fall<00:12:16.500> true<00:12:16.790> that's<00:12:17.790> a<00:12:17.850> very 00:12:18.020 --> 00:12:18.030 align:start position:0% there's no fall true that's a very 00:12:18.030 --> 00:12:20.500 align:start position:0% there's no fall true that's a very important<00:12:18.540> thing<00:12:18.720> but<00:12:19.260> it<00:12:19.410> might<00:12:19.560> not<00:12:19.740> look 00:12:20.500 --> 00:12:20.510 align:start position:0% important thing but it might not look 00:12:20.510 --> 00:12:25.640 align:start position:0% important thing but it might not look obvious<00:12:21.510> from<00:12:21.780> these<00:12:22.020> examples<00:12:24.350> so<00:12:25.350> basically 00:12:25.640 --> 00:12:25.650 align:start position:0% obvious from these examples so basically 00:12:25.650 --> 00:12:28.310 align:start position:0% obvious from these examples so basically how<00:12:25.830> this<00:12:26.010> gets<00:12:26.160> compiled<00:12:26.610> into<00:12:27.080> bytecode<00:12:28.080> is 00:12:28.310 --> 00:12:28.320 align:start position:0% how this gets compiled into bytecode is 00:12:28.320 --> 00:12:30.740 align:start position:0% how this gets compiled into bytecode is in<00:12:29.540> EVM 00:12:30.740 --> 00:12:30.750 align:start position:0% in EVM 00:12:30.750 --> 00:12:33.260 align:start position:0% in EVM it<00:12:31.200> will<00:12:31.410> do<00:12:31.500> a<00:12:31.560> couple<00:12:31.770> of<00:12:31.950> comparisons<00:12:32.550> does 00:12:33.260 --> 00:12:33.270 align:start position:0% it will do a couple of comparisons does 00:12:33.270 --> 00:12:36.440 align:start position:0% it will do a couple of comparisons does it<00:12:33.390> equal<00:12:33.540> zero<00:12:34.110> if<00:12:34.650> not<00:12:34.950> do<00:12:35.760> that<00:12:35.940> does<00:12:36.330> it 00:12:36.440 --> 00:12:36.450 align:start position:0% it equal zero if not do that does it 00:12:36.450 --> 00:12:38.690 align:start position:0% it equal zero if not do that does it equal<00:12:36.540> zero<00:12:37.080> does<00:12:37.290> it<00:12:37.410> equal<00:12:37.500> one<00:12:37.860> does<00:12:38.580> it 00:12:38.690 --> 00:12:38.700 align:start position:0% equal zero does it equal one does it 00:12:38.700 --> 00:12:43.100 align:start position:0% equal zero does it equal one does it equal<00:12:38.790> tails<00:12:39.180> if<00:12:39.990> not<00:12:40.290> else<00:12:40.640> and<00:12:41.870> the<00:12:42.870> last 00:12:43.100 --> 00:12:43.110 align:start position:0% equal tails if not else and the last 00:12:43.110 --> 00:12:46.040 align:start position:0% equal tails if not else and the last feature<00:12:43.410> we<00:12:43.800> have<00:12:43.830> is<00:12:44.250> for<00:12:44.880> loops<00:12:45.090> which<00:12:45.870> has 00:12:46.040 --> 00:12:46.050 align:start position:0% feature we have is for loops which has 00:12:46.050 --> 00:12:49.070 align:start position:0% feature we have is for loops which has an<00:12:46.170> initializer<00:12:46.620> has<00:12:47.100> a<00:12:47.540> condition<00:12:48.540> has<00:12:49.050> a 00:12:49.070 --> 00:12:49.080 align:start position:0% an initializer has a condition has a 00:12:49.080 --> 00:12:51.590 align:start position:0% an initializer has a condition has a post<00:12:49.410> block<00:12:49.590> on<00:12:49.740> the<00:12:49.830> block<00:12:50.010> now<00:12:50.600> one 00:12:51.590 --> 00:12:51.600 align:start position:0% post block on the block now one 00:12:51.600 --> 00:12:53.990 align:start position:0% post block on the block now one interesting<00:12:51.900> part<00:12:52.650> here<00:12:52.950> is<00:12:53.130> in<00:12:53.610> an 00:12:53.990 --> 00:12:54.000 align:start position:0% interesting part here is in an 00:12:54.000 --> 00:12:56.330 align:start position:0% interesting part here is in an initializer<00:12:54.480> so<00:12:55.380> actually<00:12:55.920> all<00:12:55.950> the<00:12:56.130> blocks 00:12:56.330 --> 00:12:56.340 align:start position:0% initializer so actually all the blocks 00:12:56.340 --> 00:12:58.880 align:start position:0% initializer so actually all the blocks initializer<00:12:56.940> block<00:12:57.360> and<00:12:57.570> post<00:12:57.780> block<00:12:58.020> there 00:12:58.880 --> 00:12:58.890 align:start position:0% initializer block and post block there 00:12:58.890 --> 00:13:01.610 align:start position:0% initializer block and post block there are<00:12:59.070> the<00:12:59.370> same<00:12:59.550> scope<00:12:59.900> so<00:13:00.900> any<00:13:01.080> variable 00:13:01.610 --> 00:13:01.620 align:start position:0% are the same scope so any variable 00:13:01.620 --> 00:13:03.920 align:start position:0% are the same scope so any variable created<00:13:02.070> in<00:13:02.190> the<00:13:02.280> initializer<00:13:02.700> is<00:13:03.000> valid<00:13:03.750> in 00:13:03.920 --> 00:13:03.930 align:start position:0% created in the initializer is valid in 00:13:03.930 --> 00:13:06.140 align:start position:0% created in the initializer is valid in the<00:13:04.290> for<00:13:04.500> loop<00:13:04.530> but<00:13:05.190> it's<00:13:05.370> not<00:13:05.460> valid<00:13:05.730> outside 00:13:06.140 --> 00:13:06.150 align:start position:0% the for loop but it's not valid outside 00:13:06.150 --> 00:13:09.560 align:start position:0% the for loop but it's not valid outside it<00:13:06.960> does<00:13:07.200> support<00:13:07.380> break<00:13:07.800> a<00:13:08.510> couple<00:13:09.510> of 00:13:09.560 --> 00:13:09.570 align:start position:0% it does support break a couple of 00:13:09.570 --> 00:13:15.320 align:start position:0% it does support break a couple of examples 00:13:15.320 --> 00:13:15.330 align:start position:0% 00:13:15.330 --> 00:13:19.260 align:start position:0% okay<00:13:16.890> so<00:13:17.890> we<00:13:18.010> do<00:13:18.190> actually<00:13:18.399> have<00:13:18.760> different 00:13:19.260 --> 00:13:19.270 align:start position:0% okay so we do actually have different 00:13:19.270 --> 00:13:23.639 align:start position:0% okay so we do actually have different backends<00:13:19.480> in<00:13:20.250> solidity<00:13:21.250> for<00:13:21.850> Julia<00:13:22.350> right<00:13:23.350> now 00:13:23.639 --> 00:13:23.649 align:start position:0% backends in solidity for Julia right now 00:13:23.649 --> 00:13:26.190 align:start position:0% backends in solidity for Julia right now evm<00:13:24.160> the<00:13:24.610> normally<00:13:24.940> VM<00:13:25.149> we<00:13:25.270> have<00:13:25.420> is<00:13:25.660> is<00:13:26.020> of 00:13:26.190 --> 00:13:26.200 align:start position:0% evm the normally VM we have is is of 00:13:26.200 --> 00:13:28.860 align:start position:0% evm the normally VM we have is is of course<00:13:26.410> working<00:13:26.740> and<00:13:26.920> we<00:13:27.520> have<00:13:27.550> even<00:13:28.180> 1.5 00:13:28.860 --> 00:13:28.870 align:start position:0% course working and we have even 1.5 00:13:28.870 --> 00:13:31.590 align:start position:0% course working and we have even 1.5 implemented<00:13:29.730> the<00:13:30.730> interesting<00:13:31.089> part<00:13:31.300> of<00:13:31.360> a<00:13:31.450> TV 00:13:31.590 --> 00:13:31.600 align:start position:0% implemented the interesting part of a TV 00:13:31.600 --> 00:13:35.550 align:start position:0% implemented the interesting part of a TV of<00:13:31.720> 1.5<00:13:32.260> is<00:13:32.440> that<00:13:33.010> it<00:13:33.130> supports<00:13:34.560> basically 00:13:35.550 --> 00:13:35.560 align:start position:0% of 1.5 is that it supports basically 00:13:35.560 --> 00:13:38.940 align:start position:0% of 1.5 is that it supports basically functions<00:13:35.980> and<00:13:36.300> stack<00:13:37.300> frames<00:13:37.570> and<00:13:38.410> so<00:13:38.770> it's 00:13:38.940 --> 00:13:38.950 align:start position:0% functions and stack frames and so it's 00:13:38.950 --> 00:13:41.449 align:start position:0% functions and stack frames and so it's you<00:13:39.580> know<00:13:39.700> that's<00:13:39.820> the<00:13:39.940> main<00:13:40.089> improvement 00:13:41.449 --> 00:13:41.459 align:start position:0% you know that's the main improvement 00:13:41.459 --> 00:13:44.370 align:start position:0% you know that's the main improvement what<00:13:42.459> it<00:13:42.610> means<00:13:42.820> we<00:13:43.240> can<00:13:43.510> really<00:13:44.050> easily 00:13:44.370 --> 00:13:44.380 align:start position:0% what it means we can really easily 00:13:44.380 --> 00:13:47.670 align:start position:0% what it means we can really easily translate<00:13:44.950> julia<00:13:45.339> functions<00:13:45.850> into<00:13:46.690> idiom<00:13:47.080> 1.5 00:13:47.670 --> 00:13:47.680 align:start position:0% translate julia functions into idiom 1.5 00:13:47.680 --> 00:13:50.639 align:start position:0% translate julia functions into idiom 1.5 functions<00:13:48.550> and<00:13:48.820> that<00:13:49.779> makes<00:13:50.020> it<00:13:50.140> really<00:13:50.290> easy 00:13:50.639 --> 00:13:50.649 align:start position:0% functions and that makes it really easy 00:13:50.649 --> 00:13:54.900 align:start position:0% functions and that makes it really easy to<00:13:50.860> verify<00:13:52.860> it<00:13:53.860> was<00:13:54.100> a<00:13:54.130> is<00:13:54.490> a<00:13:54.760> different 00:13:54.900 --> 00:13:54.910 align:start position:0% to verify it was a is a different 00:13:54.910 --> 00:13:57.540 align:start position:0% to verify it was a is a different back-end<00:13:55.270> which<00:13:55.870> is<00:13:56.080> in<00:13:56.230> progress<00:13:56.440> it<00:13:57.310> already 00:13:57.540 --> 00:13:57.550 align:start position:0% back-end which is in progress it already 00:13:57.550 --> 00:13:59.070 align:start position:0% back-end which is in progress it already works<00:13:57.850> but<00:13:58.240> it's<00:13:58.360> not<00:13:58.510> finished 00:13:59.070 --> 00:13:59.080 align:start position:0% works but it's not finished 00:13:59.080 --> 00:14:01.790 align:start position:0% works but it's not finished so<00:13:59.740> it's<00:13:59.860> not<00:13:59.980> really<00:14:00.190> part<00:14:00.399> of<00:14:00.520> the<00:14:00.640> tree<00:14:00.850> yet 00:14:01.790 --> 00:14:01.800 align:start position:0% so it's not really part of the tree yet 00:14:01.800 --> 00:14:04.050 align:start position:0% so it's not really part of the tree yet the<00:14:02.800> last<00:14:03.220> back-end 00:14:04.050 --> 00:14:04.060 align:start position:0% the last back-end 00:14:04.060 --> 00:14:06.690 align:start position:0% the last back-end I<00:14:04.089> think<00:14:04.570> possible<00:14:05.110> is<00:14:05.459> even<00:14:06.459> doing<00:14:06.640> a 00:14:06.690 --> 00:14:06.700 align:start position:0% I think possible is even doing a 00:14:06.700 --> 00:14:09.300 align:start position:0% I think possible is even doing a JavaScript<00:14:07.149> back-end<00:14:07.990> the<00:14:08.649> use<00:14:08.830> case<00:14:09.100> there 00:14:09.300 --> 00:14:09.310 align:start position:0% JavaScript back-end the use case there 00:14:09.310 --> 00:14:12.750 align:start position:0% JavaScript back-end the use case there would<00:14:09.520> be<00:14:09.630> someone<00:14:10.630> is<00:14:10.810> writing<00:14:11.640> you<00:14:12.640> know 00:14:12.750 --> 00:14:12.760 align:start position:0% would be someone is writing you know 00:14:12.760 --> 00:14:15.449 align:start position:0% would be someone is writing you know more<00:14:13.149> more<00:14:13.480> parts<00:14:13.779> of<00:14:13.839> the<00:14:13.899> application<00:14:14.620> they 00:14:15.449 --> 00:14:15.459 align:start position:0% more more parts of the application they 00:14:15.459 --> 00:14:17.970 align:start position:0% more more parts of the application they tap<00:14:15.730> in<00:14:16.060> solidity<00:14:16.779> right<00:14:17.470> now<00:14:17.620> you<00:14:17.680> have<00:14:17.890> to 00:14:17.970 --> 00:14:17.980 align:start position:0% tap in solidity right now you have to 00:14:17.980 --> 00:14:21.030 align:start position:0% tap in solidity right now you have to only<00:14:18.100> write<00:14:18.279> account<00:14:18.640> D<00:14:18.850> on<00:14:19.300> chains<00:14:20.020> part<00:14:20.800> in 00:14:21.030 --> 00:14:21.040 align:start position:0% only write account D on chains part in 00:14:21.040 --> 00:14:24.410 align:start position:0% only write account D on chains part in solidity<00:14:21.850> but<00:14:22.750> you<00:14:22.930> could<00:14:23.170> in<00:14:23.560> the<00:14:23.800> future 00:14:24.410 --> 00:14:24.420 align:start position:0% solidity but you could in the future 00:14:24.420 --> 00:14:27.269 align:start position:0% solidity but you could in the future right<00:14:25.420> off<00:14:25.779> chain<00:14:26.080> parts<00:14:26.410> in<00:14:26.560> solidity<00:14:27.070> and 00:14:27.269 --> 00:14:27.279 align:start position:0% right off chain parts in solidity and 00:14:27.279 --> 00:14:30.930 align:start position:0% right off chain parts in solidity and compile<00:14:28.150> those<00:14:28.300> parts<00:14:28.720> into<00:14:29.170> JavaScript<00:14:29.940> if 00:14:30.930 --> 00:14:30.940 align:start position:0% compile those parts into JavaScript if 00:14:30.940 --> 00:14:33.060 align:start position:0% compile those parts into JavaScript if anyone<00:14:31.270> volunteers<00:14:31.750> I'm<00:14:31.959> happy<00:14:32.200> to<00:14:32.320> help<00:14:32.440> to 00:14:33.060 --> 00:14:33.070 align:start position:0% anyone volunteers I'm happy to help to 00:14:33.070 --> 00:14:36.269 align:start position:0% anyone volunteers I'm happy to help to get<00:14:33.250> that<00:14:33.459> back<00:14:33.760> and<00:14:33.910> down<00:14:34.140> and<00:14:35.140> we<00:14:36.130> already 00:14:36.269 --> 00:14:36.279 align:start position:0% get that back and down and we already 00:14:36.279 --> 00:14:38.570 align:start position:0% get that back and down and we already have<00:14:36.550> a<00:14:36.580> tiny<00:14:37.330> bit<00:14:37.570> of<00:14:37.600> third-party<00:14:38.020> support 00:14:38.570 --> 00:14:38.580 align:start position:0% have a tiny bit of third-party support 00:14:38.580 --> 00:14:42.510 align:start position:0% have a tiny bit of third-party support for<00:14:39.580> Julia<00:14:40.110> there<00:14:41.110> is<00:14:41.320> a<00:14:41.560> Julia<00:14:41.950> interpreter 00:14:42.510 --> 00:14:42.520 align:start position:0% for Julia there is a Julia interpreter 00:14:42.520 --> 00:14:45.420 align:start position:0% for Julia there is a Julia interpreter named<00:14:42.640> lamp<00:14:43.230> and<00:14:44.230> that's<00:14:44.470> the<00:14:44.650> URL<00:14:44.800> for<00:14:45.190> it<00:14:45.220> I 00:14:45.420 --> 00:14:45.430 align:start position:0% named lamp and that's the URL for it I 00:14:45.430 --> 00:14:47.329 align:start position:0% named lamp and that's the URL for it I think<00:14:46.000> it<00:14:46.180> was<00:14:46.360> written<00:14:46.540> in<00:14:46.779> less<00:14:46.959> than<00:14:47.080> a<00:14:47.170> week 00:14:47.329 --> 00:14:47.339 align:start position:0% think it was written in less than a week 00:14:47.339 --> 00:14:49.650 align:start position:0% think it was written in less than a week so<00:14:48.339> they're<00:14:48.760> probably<00:14:48.910> shows<00:14:49.360> that<00:14:49.570> the 00:14:49.650 --> 00:14:49.660 align:start position:0% so they're probably shows that the 00:14:49.660 --> 00:14:52.910 align:start position:0% so they're probably shows that the language<00:14:49.990> is<00:14:50.110> quite<00:14:50.290> simple<00:14:50.740> to<00:14:50.920> deal<00:14:51.160> with<00:14:51.400> I 00:14:52.910 --> 00:14:52.920 align:start position:0% language is quite simple to deal with I 00:14:52.920 --> 00:14:57.000 align:start position:0% language is quite simple to deal with I did<00:14:53.920> a<00:14:54.070> toy<00:14:54.459> LLL<00:14:55.029> to<00:14:55.329> julia<00:14:55.690> compiler<00:14:56.110> just<00:14:56.890> to 00:14:57.000 --> 00:14:57.010 align:start position:0% did a toy LLL to julia compiler just to 00:14:57.010 --> 00:14:58.769 align:start position:0% did a toy LLL to julia compiler just to see<00:14:57.190> you<00:14:57.430> know<00:14:57.579> how<00:14:58.089> much<00:14:58.240> effort<00:14:58.390> would<00:14:58.690> it 00:14:58.769 --> 00:14:58.779 align:start position:0% see you know how much effort would it 00:14:58.779 --> 00:15:01.530 align:start position:0% see you know how much effort would it take<00:14:58.959> it<00:14:59.440> takes<00:14:59.650> a<00:14:59.740> couple<00:14:59.890> of<00:15:00.040> hours<00:15:00.220> to<00:15:01.120> write 00:15:01.530 --> 00:15:01.540 align:start position:0% take it takes a couple of hours to write 00:15:01.540 --> 00:15:04.819 align:start position:0% take it takes a couple of hours to write it<00:15:01.779> even<00:15:01.959> less<00:15:02.410> if<00:15:02.620> you<00:15:02.800> have<00:15:03.040> a<00:15:03.279> parser<00:15:03.760> ready 00:15:04.819 --> 00:15:04.829 align:start position:0% it even less if you have a parser ready 00:15:04.829 --> 00:15:08.639 align:start position:0% it even less if you have a parser ready and<00:15:05.829> lastly<00:15:06.810> you<00:15:07.810> know<00:15:07.930> with<00:15:08.079> julia<00:15:08.380> it<00:15:08.470> should 00:15:08.639 --> 00:15:08.649 align:start position:0% and lastly you know with julia it should 00:15:08.649 --> 00:15:10.470 align:start position:0% and lastly you know with julia it should be<00:15:08.770> easy<00:15:08.950> enough<00:15:09.250> to<00:15:09.610> create<00:15:10.060> domain-specific 00:15:10.470 --> 00:15:10.480 align:start position:0% be easy enough to create domain-specific 00:15:10.480 --> 00:15:13.380 align:start position:0% be easy enough to create domain-specific languages<00:15:11.230> because<00:15:12.190> julia<00:15:12.970> is<00:15:13.029> quite<00:15:13.209> low 00:15:13.380 --> 00:15:13.390 align:start position:0% languages because julia is quite low 00:15:13.390 --> 00:15:15.660 align:start position:0% languages because julia is quite low level<00:15:13.720> but<00:15:14.410> at<00:15:14.620> the<00:15:14.709> same<00:15:14.829> time<00:15:15.070> it<00:15:15.220> does<00:15:15.459> have 00:15:15.660 --> 00:15:15.670 align:start position:0% level but at the same time it does have 00:15:15.670 --> 00:15:17.579 align:start position:0% level but at the same time it does have a<00:15:15.700> lot<00:15:15.880> of<00:15:15.910> convenient<00:15:16.870> features<00:15:17.230> like 00:15:17.579 --> 00:15:17.589 align:start position:0% a lot of convenient features like 00:15:17.589 --> 00:15:22.350 align:start position:0% a lot of convenient features like functions<00:15:18.100> and<00:15:18.339> switch<00:15:18.520> statements<00:15:21.240> that<00:15:22.240> is 00:15:22.350 --> 00:15:22.360 align:start position:0% functions and switch statements that is 00:15:22.360 --> 00:15:24.630 align:start position:0% functions and switch statements that is actually<00:15:22.720> example<00:15:23.110> of<00:15:23.290> compiling 00:15:24.630 --> 00:15:24.640 align:start position:0% actually example of compiling 00:15:24.640 --> 00:15:27.660 align:start position:0% actually example of compiling LLL<00:15:25.240> to<00:15:25.390> Julia<00:15:25.690> and<00:15:25.900> as<00:15:26.830> you<00:15:26.950> can<00:15:27.100> see<00:15:27.160> most<00:15:27.580> of 00:15:27.660 --> 00:15:27.670 align:start position:0% LLL to Julia and as you can see most of 00:15:27.670 --> 00:15:31.290 align:start position:0% LLL to Julia and as you can see most of those<00:15:27.820> parts<00:15:28.320> entirely<00:15:29.320> resemble<00:15:30.300> lll 00:15:31.290 --> 00:15:31.300 align:start position:0% those parts entirely resemble lll 00:15:31.300 --> 00:15:34.320 align:start position:0% those parts entirely resemble lll counterparts<00:15:32.020> it<00:15:33.010> is<00:15:33.190> also<00:15:33.430> highlights<00:15:34.150> the 00:15:34.320 --> 00:15:34.330 align:start position:0% counterparts it is also highlights the 00:15:34.330 --> 00:15:38.190 align:start position:0% counterparts it is also highlights the need<00:15:35.200> for<00:15:35.260> optimizations<00:15:36.330> because<00:15:37.330> the<00:15:37.930> first 00:15:38.190 --> 00:15:38.200 align:start position:0% need for optimizations because the first 00:15:38.200 --> 00:15:41.730 align:start position:0% need for optimizations because the first step<00:15:38.380> in<00:15:38.800> using<00:15:39.640> julia<00:15:40.380> converting<00:15:41.380> from<00:15:41.500> any 00:15:41.730 --> 00:15:41.740 align:start position:0% step in using julia converting from any 00:15:41.740 --> 00:15:44.850 align:start position:0% step in using julia converting from any language<00:15:42.010> to<00:15:42.220> julia<00:15:42.670> is<00:15:43.350> to<00:15:44.350> be<00:15:44.470> able<00:15:44.560> to 00:15:44.850 --> 00:15:44.860 align:start position:0% language to julia is to be able to 00:15:44.860 --> 00:15:48.930 align:start position:0% language to julia is to be able to ensure<00:15:46.080> the<00:15:47.080> code<00:15:47.320> is<00:15:47.470> correct<00:15:47.860> so<00:15:48.520> it<00:15:48.640> will<00:15:48.790> be 00:15:48.930 --> 00:15:48.940 align:start position:0% ensure the code is correct so it will be 00:15:48.940 --> 00:15:51.510 align:start position:0% ensure the code is correct so it will be verbose<00:15:49.620> there<00:15:50.620> won't<00:15:50.770> be<00:15:50.830> any<00:15:51.010> optimization 00:15:51.510 --> 00:15:51.520 align:start position:0% verbose there won't be any optimization 00:15:51.520 --> 00:15:54.570 align:start position:0% verbose there won't be any optimization at<00:15:51.640> that<00:15:51.790> level<00:15:52.000> and<00:15:52.300> the<00:15:53.140> next<00:15:53.440> step<00:15:53.650> one<00:15:54.370> can 00:15:54.570 --> 00:15:54.580 align:start position:0% at that level and the next step one can 00:15:54.580 --> 00:15:57.180 align:start position:0% at that level and the next step one can apply<00:15:54.840> simple<00:15:55.840> optimizations<00:15:56.470> step<00:15:56.710> by<00:15:56.890> step 00:15:57.180 --> 00:15:57.190 align:start position:0% apply simple optimizations step by step 00:15:57.190 --> 00:16:00.330 align:start position:0% apply simple optimizations step by step so<00:15:57.760> in<00:15:57.940> this<00:15:58.090> case<00:15:58.300> here<00:15:58.600> I<00:15:59.010> would<00:16:00.010> want<00:16:00.220> the 00:16:00.330 --> 00:16:00.340 align:start position:0% so in this case here I would want the 00:16:00.340 --> 00:16:02.550 align:start position:0% so in this case here I would want the LLL<00:16:00.670> -<00:16:00.820> Julia<00:16:01.120> compiler<00:16:01.510> to<00:16:01.750> output<00:16:02.140> this<00:16:02.290> code 00:16:02.550 --> 00:16:02.560 align:start position:0% LLL - Julia compiler to output this code 00:16:02.560 --> 00:16:05.400 align:start position:0% LLL - Julia compiler to output this code but<00:16:03.340> it's<00:16:03.760> not<00:16:03.820> really<00:16:04.090> optimized<00:16:04.480> so<00:16:05.230> the 00:16:05.400 --> 00:16:05.410 align:start position:0% but it's not really optimized so the 00:16:05.410 --> 00:16:08.130 align:start position:0% but it's not really optimized so the next<00:16:05.590> step<00:16:05.830> I<00:16:06.100> would<00:16:06.460> want<00:16:06.760> an<00:16:06.880> optimizer<00:16:07.330> to 00:16:08.130 --> 00:16:08.140 align:start position:0% next step I would want an optimizer to 00:16:08.140 --> 00:16:12.180 align:start position:0% next step I would want an optimizer to inline<00:16:08.560> a<00:16:08.860> node<00:16:09.240> so<00:16:10.240> below<00:16:10.960> get<00:16:11.920> owner 00:16:12.180 --> 00:16:12.190 align:start position:0% inline a node so below get owner 00:16:12.190 --> 00:16:15.180 align:start position:0% inline a node so below get owner wouldn't<00:16:12.670> call<00:16:12.880> node<00:16:13.390> it<00:16:13.810> would<00:16:14.530> just<00:16:14.800> have 00:16:15.180 --> 00:16:15.190 align:start position:0% wouldn't call node it would just have 00:16:15.190 --> 00:16:19.350 align:start position:0% wouldn't call node it would just have called<00:16:15.580> data<00:16:16.320> as<00:16:17.320> code<00:16:18.040> eight<00:16:18.190> a<00:16:18.220> load<00:16:18.490> as<00:16:19.120> an 00:16:19.350 --> 00:16:19.360 align:start position:0% called data as code eight a load as an 00:16:19.360 --> 00:16:24.050 align:start position:0% called data as code eight a load as an instruction<00:16:21.960> so<00:16:22.960> that's<00:16:23.170> just<00:16:23.320> an<00:16:23.470> overview 00:16:24.050 --> 00:16:24.060 align:start position:0% instruction so that's just an overview 00:16:24.060 --> 00:16:25.950 align:start position:0% instruction so that's just an overview what<00:16:25.060> happened<00:16:25.390> in<00:16:25.480> the<00:16:25.570> last<00:16:25.690> couple<00:16:25.780> of 00:16:25.950 --> 00:16:25.960 align:start position:0% what happened in the last couple of 00:16:25.960 --> 00:16:28.980 align:start position:0% what happened in the last couple of months<00:16:26.140> regarding<00:16:27.070> solidity<00:16:27.460> and<00:16:27.670> Julia<00:16:27.990> and 00:16:28.980 --> 00:16:28.990 align:start position:0% months regarding solidity and Julia and 00:16:28.990 --> 00:16:31.830 align:start position:0% months regarding solidity and Julia and as<00:16:29.110> you<00:16:29.200> can<00:16:29.320> see<00:16:29.380> in<00:16:29.770> point<00:16:30.550> 12<00:16:30.940> we<00:16:31.810> have 00:16:31.830 --> 00:16:31.840 align:start position:0% as you can see in point 12 we have 00:16:31.840 --> 00:16:34.380 align:start position:0% as you can see in point 12 we have released<00:16:32.470> support<00:16:33.250> for<00:16:33.370> functions<00:16:33.820> for<00:16:34.150> loops 00:16:34.380 --> 00:16:34.390 align:start position:0% released support for functions for loops 00:16:34.390 --> 00:16:38.790 align:start position:0% released support for functions for loops and<00:16:35.340> point<00:16:36.340> 17<00:16:36.910> which<00:16:37.660> was<00:16:37.690> recently<00:16:38.200> the 00:16:38.790 --> 00:16:38.800 align:start position:0% and point 17 which was recently the 00:16:38.800 --> 00:16:42.960 align:start position:0% and point 17 which was recently the added<00:16:39.070> support<00:16:39.280> for<00:16:39.910> a<00:16:40.170> new<00:16:41.170> ABI<00:16:41.590> encoder<00:16:42.070> so 00:16:42.960 --> 00:16:42.970 align:start position:0% added support for a new ABI encoder so 00:16:42.970 --> 00:16:46.260 align:start position:0% added support for a new ABI encoder so many<00:16:43.180> people<00:16:43.510> who<00:16:43.810> were<00:16:44.770> complaining<00:16:45.280> the 00:16:46.260 --> 00:16:46.270 align:start position:0% many people who were complaining the 00:16:46.270 --> 00:16:49.680 align:start position:0% many people who were complaining the lack<00:16:46.480> of<00:16:46.510> support<00:16:47.020> for<00:16:47.230> structs<00:16:48.180> that<00:16:49.180> new<00:16:49.360> ABI 00:16:49.680 --> 00:16:49.690 align:start position:0% lack of support for structs that new ABI 00:16:49.690 --> 00:16:53.160 align:start position:0% lack of support for structs that new ABI encoder<00:16:50.140> enables<00:16:50.980> support<00:16:51.940> for<00:16:52.300> passing 00:16:53.160 --> 00:16:53.170 align:start position:0% encoder enables support for passing 00:16:53.170 --> 00:16:55.620 align:start position:0% encoder enables support for passing structs<00:16:53.590> between<00:16:53.920> functions<00:16:54.430> now<00:16:55.240> that's 00:16:55.620 --> 00:16:55.630 align:start position:0% structs between functions now that's 00:16:55.630 --> 00:16:57.300 align:start position:0% structs between functions now that's already<00:16:55.840> in<00:16:56.020> the<00:16:56.110> compiler<00:16:56.500> but<00:16:56.770> it<00:16:56.890> has<00:16:57.040> to<00:16:57.190> be 00:16:57.300 --> 00:16:57.310 align:start position:0% already in the compiler but it has to be 00:16:57.310 --> 00:17:00.710 align:start position:0% already in the compiler but it has to be enabled<00:16:57.490> by<00:16:57.940> a<00:16:57.970> special<00:16:58.680> experimental<00:16:59.680> switch 00:17:00.710 --> 00:17:00.720 align:start position:0% enabled by a special experimental switch 00:17:00.720 --> 00:17:03.510 align:start position:0% enabled by a special experimental switch because<00:17:01.720> you<00:17:02.080> know<00:17:02.170> we're<00:17:02.350> not<00:17:02.500> we're<00:17:03.370> not 00:17:03.510 --> 00:17:03.520 align:start position:0% because you know we're not we're not 00:17:03.520 --> 00:17:05.069 align:start position:0% because you know we're not we're not really<00:17:03.700> confident<00:17:04.060> yet<00:17:04.329> that<00:17:04.750> it<00:17:04.839> should<00:17:04.990> be 00:17:05.069 --> 00:17:05.079 align:start position:0% really confident yet that it should be 00:17:05.079 --> 00:17:06.840 align:start position:0% really confident yet that it should be used<00:17:05.260> in<00:17:05.410> production<00:17:05.650> but<00:17:06.310> if<00:17:06.430> someone<00:17:06.699> wants 00:17:06.840 --> 00:17:06.850 align:start position:0% used in production but if someone wants 00:17:06.850 --> 00:17:09.470 align:start position:0% used in production but if someone wants to<00:17:06.910> try<00:17:07.150> out<00:17:07.180> it<00:17:07.480> it's<00:17:07.690> certainly<00:17:08.020> possible 00:17:09.470 --> 00:17:09.480 align:start position:0% to try out it it's certainly possible 00:17:09.480 --> 00:17:12.630 align:start position:0% to try out it it's certainly possible hopefully<00:17:10.480> the<00:17:10.870> next<00:17:11.140> release<00:17:11.410> we<00:17:12.220> will<00:17:12.370> have 00:17:12.630 --> 00:17:12.640 align:start position:0% hopefully the next release we will have 00:17:12.640 --> 00:17:15.480 align:start position:0% hopefully the next release we will have a<00:17:12.910> new<00:17:13.420> ABI<00:17:13.780> decoder<00:17:14.260> merged<00:17:15.070> at<00:17:15.250> the<00:17:15.310> same 00:17:15.480 --> 00:17:15.490 align:start position:0% a new ABI decoder merged at the same 00:17:15.490 --> 00:17:19.260 align:start position:0% a new ABI decoder merged at the same time<00:17:15.760> and<00:17:16.000> that<00:17:16.810> will<00:17:17.020> enable<00:17:18.030> functions<00:17:19.030> to 00:17:19.260 --> 00:17:19.270 align:start position:0% time and that will enable functions to 00:17:19.270 --> 00:17:21.840 align:start position:0% time and that will enable functions to receive<00:17:19.630> structs<00:17:20.079> because<00:17:20.770> right<00:17:21.010> now<00:17:21.220> you 00:17:21.840 --> 00:17:21.850 align:start position:0% receive structs because right now you 00:17:21.850 --> 00:17:23.670 align:start position:0% receive structs because right now you can<00:17:22.060> send<00:17:22.390> structs<00:17:22.870> but<00:17:23.020> you<00:17:23.140> cannot<00:17:23.320> receive 00:17:23.670 --> 00:17:23.680 align:start position:0% can send structs but you cannot receive 00:17:23.680 --> 00:17:26.699 align:start position:0% can send structs but you cannot receive structs<00:17:24.160> and<00:17:24.660> then<00:17:25.660> hopefully<00:17:25.839> to<00:17:26.260> releases 00:17:26.699 --> 00:17:26.709 align:start position:0% structs and then hopefully to releases 00:17:26.709 --> 00:17:30.570 align:start position:0% structs and then hopefully to releases from<00:17:26.920> now<00:17:27.070> we<00:17:27.880> will<00:17:28.000> have<00:17:28.270> a<00:17:28.860> first<00:17:29.860> version<00:17:30.400> of 00:17:30.570 --> 00:17:30.580 align:start position:0% from now we will have a first version of 00:17:30.580 --> 00:17:33.660 align:start position:0% from now we will have a first version of a<00:17:30.640> solidity<00:17:31.180> to<00:17:31.510> julia<00:17:32.050> compiler<00:17:32.500> as<00:17:33.250> part<00:17:33.550> of 00:17:33.660 --> 00:17:33.670 align:start position:0% a solidity to julia compiler as part of 00:17:33.670 --> 00:17:37.690 align:start position:0% a solidity to julia compiler as part of solidity<00:17:34.300> and<00:17:34.600> then<00:17:35.410> in<00:17:35.530> the<00:17:35.590> future<00:17:35.710> he<00:17:36.640> was 00:17:37.690 --> 00:17:37.700 align:start position:0% solidity and then in the future he was 00:17:37.700 --> 00:17:40.790 align:start position:0% solidity and then in the future he was so<00:17:38.700> it<00:17:38.790> can<00:17:38.910> be<00:17:39.000> already<00:17:39.420> tried<00:17:40.200> out<00:17:40.230> if<00:17:40.620> you 00:17:40.790 --> 00:17:40.800 align:start position:0% so it can be already tried out if you 00:17:40.800 --> 00:17:43.160 align:start position:0% so it can be already tried out if you dare<00:17:41.040> those<00:17:41.730> are<00:17:41.880> the<00:17:41.940> command-line<00:17:42.270> options 00:17:43.160 --> 00:17:43.170 align:start position:0% dare those are the command-line options 00:17:43.170 --> 00:17:46.550 align:start position:0% dare those are the command-line options to<00:17:44.040> use<00:17:44.280> the<00:17:44.520> solidity<00:17:44.850> compiler<00:17:45.390> to<00:17:45.810> compile 00:17:46.550 --> 00:17:46.560 align:start position:0% to use the solidity compiler to compile 00:17:46.560 --> 00:17:48.560 align:start position:0% to use the solidity compiler to compile assembly<00:17:46.950> and<00:17:47.700> you<00:17:48.000> can<00:17:48.120> also<00:17:48.270> switch<00:17:48.510> to 00:17:48.560 --> 00:17:48.570 align:start position:0% assembly and you can also switch to 00:17:48.570 --> 00:17:49.490 align:start position:0% assembly and you can also switch to julia<00:17:49.020> mode 00:17:49.490 --> 00:17:49.500 align:start position:0% julia mode 00:17:49.500 --> 00:17:52.810 align:start position:0% julia mode the<00:17:49.950> only<00:17:50.100> difference<00:17:50.490> there<00:17:50.670> is<00:17:50.910> using<00:17:51.840> types 00:17:52.810 --> 00:17:52.820 align:start position:0% the only difference there is using types 00:17:52.820 --> 00:17:56.780 align:start position:0% the only difference there is using types at<00:17:53.820> the<00:17:53.970> last<00:17:54.120> line<00:17:54.300> is<00:17:54.600> changing<00:17:55.580> the<00:17:56.580> output 00:17:56.780 --> 00:17:56.790 align:start position:0% at the last line is changing the output 00:17:56.790 --> 00:18:01.460 align:start position:0% at the last line is changing the output machine<00:17:59.090> if<00:18:00.090> you're<00:18:00.450> interested<00:18:00.900> in<00:18:00.990> Julia<00:18:01.260> or 00:18:01.460 --> 00:18:01.470 align:start position:0% machine if you're interested in Julia or 00:18:01.470 --> 00:18:03.800 align:start position:0% machine if you're interested in Julia or solidity<00:18:02.070> development<00:18:02.730> and<00:18:02.970> you<00:18:03.540> can<00:18:03.660> join 00:18:03.800 --> 00:18:03.810 align:start position:0% solidity development and you can join 00:18:03.810 --> 00:18:07.910 align:start position:0% solidity development and you can join the<00:18:03.990> solidity<00:18:04.410> -<00:18:04.890> dev<00:18:05.490> channel<00:18:06.060> on<00:18:06.300> Gator<00:18:07.140> or 00:18:07.910 --> 00:18:07.920 align:start position:0% the solidity - dev channel on Gator or 00:18:07.920 --> 00:18:09.260 align:start position:0% the solidity - dev channel on Gator or you<00:18:08.070> can<00:18:08.220> just<00:18:08.400> talk<00:18:08.550> to<00:18:08.580> me<00:18:08.790> directly 00:18:09.260 --> 00:18:09.270 align:start position:0% you can just talk to me directly 00:18:09.270 --> 00:18:16.540 align:start position:0% you can just talk to me directly ataxic<00:18:09.960> on<00:18:10.260> Gator<00:18:10.740> thank<00:18:11.580> you 00:18:16.540 --> 00:18:16.550 align:start position:0% 00:18:16.550 --> 00:18:24.130 align:start position:0% [Music]